Thanks. Is there any relation to https://bugs.kde.org/show_bug.cgi?id=420599?

Related fix in KEXI 3.2 would be welcome.

For now when such a "table" table is open in data view, it looks strange:

And the console shows:

Cannot open cursor
--aborting setData().
 CURSOR(KDbQuerySchema:"SELECT [id] FROM [table] ORDER BY [id]"
 NOT_OPENED  NOT_BUFFERED AT=-1)

Instead error should be presented and the tab should not be open.

To be sure, you're constructing a query using C++ classes and not using the parser?
I am asking because to me "select id from [table]" does not work since we do not (yet) support identifier escaping with [].

Another note so we won't forget. Update for autotests (both positive and negative). Here's the branch https://bugs.kde.org/show_bug.cgi?id=332161#c8

In D29277#659787, @staniek wrote:

Thanks. Is there any relation to https://bugs.kde.org/show_bug.cgi?id=420599?

Yes, this is related to both https://bugs.kde.org/show_bug.cgi?id=420599 and https://bugs.kde.org/show_bug.cgi?id=332161 .

In D29277#659798, @staniek wrote:

To be sure, you're constructing a query using C++ classes and not using the parser?
I am asking because to me "select id from [table]" does not work since we do not (yet) support identifier escaping with [].

I modified KDb in my local machine to accept quoted identifiers using back quotes (this is related to the comment i just posted to https://bugs.kde.org/show_bug.cgi?id=332161) and i was trying it out with an unmodified version of Kexi, to see what issues it raises. Thus i saw the problem this commit fixes using the parser through Kexi, but i assumed that it would be the same using C++ to construct the query, that is why i sent the fix. Also, it will be a problem once KDb has quoted identifiers.

I understand this makes it hard for you to test the changes, though.

Entering "select id from [table]" in KEXI SQL editor or passing it to a parser in C++ raises the same parser's error.
In order to reproduce bug you're fixing above one needs to create a queryfully using the C++ API since the parser won't let the to go reserved identifiers through.
(until the #332161 is solved)

As for using back quotes for any testing. This is not going to be in any user/developer -visible SQL. Only [ ] and Wiki Home Page are. The idea for back quotes is the storage format of KEXI queries to be compatible.

In D29277#659789, @staniek wrote:

Related fix in KEXI 3.2 would be welcome.

Created potential fix for this in D29286

In D29277#659924, @staniek wrote:

Entering "select id from [table]" in KEXI SQL editor or passing it to a parser in C++ raises the same parser's error.
In order to reproduce bug you're fixing above one needs to create a queryfully using the C++ API since the parser won't let the to go reserved identifiers through.
(until the #332161 is solved)

At present, until #332161 is implemented, this is the only way of triggering this bug, as far as i know.

As for using back quotes for any testing. This is not going to be in any user/developer -visible SQL. Only [ ] and [[]] are. The idea for back quotes is the storage format of KEXI queries to be compatible.

Sorry, i did my tests before our discussion in #332161 and was trying out my misconceptions of the conclusions there. I reverted all my changes and will try again with [].