It is weird, it does not happen in B4J.
The issue also happen when the initial table is created with more than one column.
The issue is still persist if LIMIT 1 is removed or even if LIMIT 10 is used.
Not the last select but if the query has executed before.
e.g.
Query 1: SELECT * FROM client LIMIT 10
Query 2: SELECT * FROM client LIMIT 20 ' rs.ColumnCount: 4
Query 3: SELECT * FROM client LIMIT 10 ' rs.ColumnCount: 1 <-- it seems results of query 1 is cached
I think it is caused by a feature call
page cache
Source:
https://www.sqlite.org/draft/fileio.html
My suggestion is to use the following query if you want to check for table columns.
SQL:
PRAGMA table_info(client)