You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run the qxBlogCompositeKey example,produce a qxBlogCompositeKey.sqlite db file.
I check it with DB Browser for SQLite,the table not have any primary key.
Test with QxOrm version 1.4.8.
And the fixed issue SQL DISTINCT keyword in qx::QxSqlQuery (qx::dao::execte_query) class (when DISTINCT is used, then the primary key is not fetched) still reproduced.
The text was updated successfully, but these errors were encountered:
About qxBlogCompositeKey.sqlite file and primary keys :
As explained in the documentation here : https://www.qxorm.com/qxorm_en/manual.html#manual_470
The function qx::dao::create_table can be used to create examples or prototypes.
To manage correctly your database schema, you have to use a tool dedicated to your SGBD (pgAdmin for PostgreSQL for example) or QxEntityEditor application.
The qxBlogCompositeKey test project is valid (even without primary keys defined in the schema) : the values in each column are correct.
About SQL DISTINCT : sorry I don't understand.
Could you please provide more details ?
Run the qxBlogCompositeKey example,produce a qxBlogCompositeKey.sqlite db file.
I check it with DB Browser for SQLite,the table not have any primary key.
Test with QxOrm version 1.4.8.
And the fixed issue SQL DISTINCT keyword in qx::QxSqlQuery (qx::dao::execte_query) class (when DISTINCT is used, then the primary key is not fetched) still reproduced.
The text was updated successfully, but these errors were encountered: