ambigious column name '...' --------------------------- Key: CORE-6544 URL: http://tracker.firebirdsql.org/browse/CORE-6544 Project: Firebird Core Issue Type: Improvement Environment: Win10, x64 Reporter: Alexander Muylaert Attachments: image_2021_04_21T05_29_28_939Z.png
Hi We had an accidental performance degrade because of a calculated field that should wasn't intended to be used in production. The problem behind it was the SQL that was approved. It contained ambiguous column names between tables. It would be magnificent if you could fail on compile time, since this is a very dangerous situation. In my example, bit T_ADDRESS and T_PROJECT have a field F_PERS_ID and the code I'm showing is the computed by of a calculated field. The second (correct) implementation gives me a correct, fast result, while the first one, returns a full table scan. What it should do... But it would have saved us many stupid hours of debugging if the ambiguous warning would have been thrown. A bit like in MS-SQL. kind regards Alexander -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel