It happens in 2.5.1. How do I file a bug report?
CREATE TABLE TEST_TABLE
(
ID INTEGER,
COMPUTED_COL VARCHAR(6) COMPUTED BY ('FAILED')
);
SELECT t.COMPUTED_COL
FROM RDB$DATABASE r
LEFT JOIN TEST_TABLE t
ON r.RDB$RELATION_ID = t.ID
COMPUTED_COL
------------
FAILED
-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Rick Debay
Sent: Thursday, May 31, 2012 11:15 AM
To: firebird-support@yahoogroups.com
Subject: RE: [firebird-support] Left join and computed columns
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,
> A query with a left join to a table with a computed column returned
> 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
be expected.
> 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
------------------------------------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Visit http://www.firebirdsql.org and click the Resources item on the
main (top) menu. Try Knowledgebase and FAQ links !
Also search the knowledgebases at http://www.ibphoenix.com
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Yahoo! Groups Links
Disclaimer: This message (including attachments) is confidential and may be
privileged. If you have received it by mistake please notify the sender by
return e-mail and delete this message from your system. Any unauthorized use or
dissemination of this message in whole or in part is strictly prohibited.
Please note that e-mails are susceptible to change. RxStrategies, Inc. shall
not be liable for the improper or incomplete transmission of the information
contained in this communication or for any delay in its receipt or damage to
your system. RxStrategies, Inc. does not guarantee that the integrity of this
communication has been maintained nor that this communication is free from
viruses, interceptions or interference.
