Subject | RE: [firebird-support] Left join and computed columns |
---|---|
Author | Rick Debay |
Post date | 2012-05-31T15:15:21Z |
I'll test in 2.5.1 and file a bug report.
-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Leyne, Sean
Sent: Friday, May 25, 2012 1:04 PM
To: firebird-support@yahoogroups.com
Subject: RE: [firebird-support] Left join and computed columns - Email
found in subject
Rick,
sense of it.
My initial thinking was that was as expected, but in thinking further...
If no row in the LEFT table exists, then all columns for the row should
be NULL, so this would be a bug.
Sean
-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Leyne, Sean
Sent: Friday, May 25, 2012 1:04 PM
To: firebird-support@yahoogroups.com
Subject: RE: [firebird-support] Left join and computed columns - Email
found in subject
Rick,
> A query with a left join to a table with a computed column returnedbe expected.
> values in the computed column even though the row didn't exist in the
> table. All other non-computed values came back as null, which was to
> Is this a bug, or correct by SQL specifications?I don't have a copy of SQL standard or the required decoder ring to make
sense of it.
My initial thinking was that was as expected, but in thinking further...
If no row in the LEFT table exists, then all columns for the row should
be NULL, so this would be a bug.
Sean