<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Firebird SQL: INSERT INTO...SELECT" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124069#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Firebird SQL: INSERT INTO...SELECT" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124069">bug 124069</a> from <a class="email" href="mailto:drewjensen.inbox@gmail.com" title="Drew Jensen <drewjensen.inbox@gmail.com>"> Drew Jensen</a> <pre>After reading a couple threads on the Firebird ML it seems this needs a little different explanation. The issue with the quoting being different between SELECT and INSERT is LibreOffice added it seems. To see this in action start with a create statement in the SQL window which does not quote any identifier ie: create table b1 (id integer, dat varchar(15)) Now the rule is that all unquoted identifiers are cast to uppercase. The table name is B1 and fields are ID and DAT. Back in the SQL window however libreoffice will quote identifiers used in select statements. So entering select id from b1 will throw an error (table b1 not found) precisely because the LO parser added the quotes. While using the API via Basic; execute command does not quote identifiers in the string executequery does so; stmt.execute( "select id from b1") passes because the FB engine cast identifiers to uppercase. stmt.executequery fails with error 'table b1 not found' because the identifiers where quoted. All the GUI tools in Base default to mixed case identifiers so when any DML needing execute vs executequery all the identifiers would need to be quoted explicitly. Long way to say it would look like a feature request to update the LO parser for UPDATE, INSERT, etc rather than a bug. A platform nuance worth space in the documentation me thinks also.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>