https://bugs.kde.org/show_bug.cgi?id=420599
--- Comment #6 from jordi fita i mas <jf...@infoblitz.com> --- >> Using [] to escape identifiers would free the double quotes to be used >> only for string literals, but it seems to me that >> KDbNativeStatementBuilder, or KDB::escapeIdentifier, should still be >> corrected to use the proper KDbSql escape characters. > > Is this still the case given what I said above? I believe it is, yes. When i open the query from the attached database, using Kexi 3.2 or 3.3, in text view it is true that the displayed SQL remains unchanged, as you said, but when switching to data view all the rows have a value of 'group', even though the source table, the one with the "group" column, has only integers; design view the expression under “query columns” is now “expr1: 'group'”. Moreover, if i make any change to the query in design mode, for example toggling twice the visible check box, and *then* switch to text view without saving the query, it changes again to SELECT 'group' AS expr1 FROM source. Checking with sqlite3 the value stored in kexi__objectdata, it outputs: > sqlite> select * from kexi__objectdata where o_sub_id = 'sql'; > 2|SELECT "group" FROM source|sql > sqlite> If i am not mistaken, it means that KDbNativeStatementBuilder generated a statement with the column quoted as "group" straight from the KDbQuerySchema, but KDbParser reads it as if it were: SELECT 'group' AS expr1 FROM source Thus, even if KDbParser could read columns quoted [as this], unless KDbNativeStatementBuilder used [ and ] as quote characters, the problem would still be there, wouldn’t it? Sorry if a am not making any sense; i must not understand something from KDb internals :) -- You are receiving this mail because: You are watching all bug changes.
