@qxorm said in QxOrm 1.5.0 and QxEntityEditor 1.2.8 released (Qt ORM/ODM):
Hello,
QxOrm library 1.5.0 and QxEntityEditor application 1.2.8 just released.
QxOrm library 1.5.0 changes log :
Fix qx::dao::fetch_by_id_with_relation() when a table alias is used (table alias is now used in the WHERE part instead of table name)
Fix qx::IxDataMember::getType() method when used in a multi-thread environment
New method qx::IxSqlRelation::linkRelationKeyTo() for MongoDB database to simulate lazy loading for relationships (GitHub #107)
Fix qx::QxSqlDatabase and multi-thread issue when the OS assigns an old and destroyed thread identifier to a new one (GitHub #42) + add method qx::QxSqlDatabase::removeDatabaseByThread() to call at the end of a thread execution
Fix qx::QxSimpleCrypt class with Qt version >= 5.10 and error "Attempted to overwrite a QRandomGenerator to system() or global()"
Fix database not opened using async queries (GitHub #109)
QxEntityEditor application 1.2.8 changes log :
New export plugin 'QxEESourceControlExport' : export a *.qxee QxEntityEditor project file to a list of JSON files which can be easily check-in in a source control repository (Git, Perforce, CVS, etc...)
New import plugin 'QxEESourceControlImport' : import a list of JSON files (generated using 'QxEESourceControlExport' export plugin) inside a *.qxee QxEntityEditor project file
These 2 new plugins allow a team development to work simultaneously on a same *.qxee QxEntityEditor project file
A typical workflow could be (with 2 developers named dev A and dev B) :
dev A and dev B work on a same *.qxee QxEntityEditor project file
dev A create/modify/change some entities in QxEntityEditor application
dev B create/modify/change other entities in QxEntityEditor application
dev A and dev B export the *.qxee project file using the new 'QxEESourceControlExport' export plugin
Once exported, dev A and dev B check-in the JSON files inside the source control manager (Git, Perforce, CVS, etc...) on their own branch
dev A and dev B integrate from their own branch to the DEV (or MAIN or MASTER) branch (if there are some conflicts to resolve, it should be easy because JSON files are easy to read and understand)
dev A and dev B can now get latest JSON files from the DEV (or MAIN or MASTER) branch : these JSON files contain both modifications from dev A and dev B
dev A and dev B can import these JSON files inside QxEntityEditor application using the new 'QxEESourceControlImport' import plugin
These 2 new plugins can be executed using command line (like all other QxEntityEditor plugins), here are 2 examples :
Export : QxEntityEditor --no_gui --project="C:\Temp\qxBlog.qxee" --plugin=QxEESourceControlExport --QxEESourceControlExport_path="C:\Temp\source_control"
Import : QxEntityEditor --no_gui --project="C:\Temp\qxBlog.qxee" --plugin=QxEESourceControlImport --QxEESourceControlImport_path="C:\Temp\source_control\qxBlog.qxee.export.json"
The recent updates for QxOrm library and QxEntityEditor application bring several important improvements:
QxOrm Library 1.5.0 includes fixes for issues like table alias handling in queries, multi-threading problems, and database async queries. New features include a method for simulating lazy loading in MongoDB and improvements to handle thread identifiers and cryptographic functions.
QxEntityEditor 1.2.8 introduces new plugins for source control integration. The QxEESourceControlExport and QxEESourceControlImport plugins facilitate team development by allowing multiple developers to export and import .qxee project files as JSON, which can be easily managed in source control systems like Git or CVS. These plugins support a streamlined workflow for simultaneous project modifications and conflict resolution.
For more details and to use these new features, refer to the QxOrm and QxEntityEditor documentation or the GitHub repository.
