QxEntityEditor 1.2.1 known issues

Forum for posting problems using QxEntityEditor

QxEntityEditor 1.2.1 known issues

Postby qxorm » Thu Dec 22, 2016 8:30 am

Hello,

Here is a list of known issues and workarounds found with QxEntityEditor 1.2.1 (by customers and/or open source community) :

1- Bug after an import process : after using an import plugin (import from database structure, import from JSON), the project is not stable (no crash, but strange behaviour, loosing properties, bad C++ export). This is a regression compared to previous version QxEntityEditor 1.1.9, and it will be fixed quickly.
WORKAROUND : after an import process, just reload the project (after reloading the project, when import is finished, then qxee project becomes stable) :
- using F5 keyboard ;
- or using main menu : File >> Reload project ;
- or closing QxEntityEditor and re-open it.

EDIT : here are the links to download a BETA version of QxEntityEditor 1.2.2 with the fix for the above issue (bug after an import process) :
- win 32b : https://www.qxorm.com/version/QxEntityE ... in_32b.zip
- linux 64b : https://www.qxorm.com/version/QxEntityE ... 64b.tar.gz

Please let me know if you find any other issues and/or regressions.
qxorm
Site Admin
 
Posts: 406
Joined: Mon Apr 12, 2010 7:45 am

Re: QxEntityEditor 1.2.1 known issues

Postby jimmytaker » Fri Dec 23, 2016 11:22 pm

Hey,

I found two more issues:

1. Column names are not escaped in the mysql generated .sql, so having an sql word such as "order" as a column name does not work.
e.g.
bad:

Code: Select all
CREATE TABLE t_test (test_id INTEGER NOT NULL AUTO_INCREMENT, order SMALLINT, PRIMARY KEY (test_id));


good:

Code: Select all
CREATE TABLE `t_test` (`test_id` INTEGER NOT NULL AUTO_INCREMENT, `order` SMALLINT, PRIMARY KEY (`test_id`));


I attach test files.
orderColumn.rar
Contains a QxEntityEditor and MySql export
(5 KiB) Downloaded 20 times


2. N to N relationships cannot be imported. Exporting the attached file to MySQL, creating a new project and importing the MySQL db imports 3 separate entities instead of the NtoN relationship.
NtoN.rar
NtoN relationship problem
(10.41 KiB) Downloaded 20 times
Last edited by jimmytaker on Sun Jan 01, 2017 6:12 am, edited 1 time in total.
jimmytaker
 
Posts: 18
Joined: Fri Dec 23, 2016 11:04 pm

Re: QxEntityEditor 1.2.1 known issues

Postby jimmytaker » Fri Dec 23, 2016 11:31 pm

A small wish - would be nice if the projects in recent project had full path in addition to the project name, so that same name projects can be distinguished. Same applies for the window title bar.
jimmytaker
 
Posts: 18
Joined: Fri Dec 23, 2016 11:04 pm

Re: QxEntityEditor 1.2.1 known issues

Postby qxorm » Sat Dec 24, 2016 1:22 pm

Hello,

Column names are not escaped in the mysql generated .sql, so having an sql word such as "order" as a column name does not work.

I didn't know about about column name escape in MySql, thx, it will be fixed.

N to N relationships cannot be imported. Exporting the attached file to MySQL, creating a new project and importing the MySQL db imports 3 separate entities instead of the NtoN relationship.

Yes this is normal, a n-n relationship is always splitted in 2 relationships 1-n and n-1 when importing.
It should not be a problem : do you have any error msg ?

would be nice if the projects in recent project had full path in addition to the project name

Yes, this is a good idea, thank you, it will be done.
qxorm
Site Admin
 
Posts: 406
Joined: Mon Apr 12, 2010 7:45 am

Re: QxEntityEditor 1.2.1 known issues

Postby jimmytaker » Sun Dec 25, 2016 9:05 pm

On the NtoN relationship - no error, just as you described. But this forces you to use QxEntityEditor for the DB design (or you have to adapt it quite a bit after an import). It sort of makes the import function much less useful. I realize guessing whether an NtoN is present might not be straighforward, but it would be a nice feature. You can count this as a feature request ;)
jimmytaker
 
Posts: 18
Joined: Fri Dec 23, 2016 11:04 pm

Re: QxEntityEditor 1.2.1 known issues

Postby jimmytaker » Mon Dec 26, 2016 4:17 am

I found another bug in the code generator. This one is quite nasty and leads to assert failure.
It is hard to explain, but I will try. You can reproduce it with the attached project
QxPMDB.rar
Generates buggy code.
(11.04 KiB) Downloaded 19 times
. Generate the code and then try this:
Code: Select all
   rotor_variant tmp;
   tmp.setrotor_variant_id(2);
   tmp.tests(true);

I figured out why this happens. From the generated classes:
Code: Select all
   pRelation = t.relationOneToMany(& rotor_variant::m_tests, "tests", "rotor_variant_id", 0); //from rotor_variant.gen.cpp
   pRelation = t.relationManyToOne(& test::m_rotor_variant, "rotor_variant", 0); //from test.gen.cpp

The problem is that the name of the relationship name should be the same in both. Or it does not get found, because the collection contains the other name. I have changed the name of the relationship in the QxEntityEditor.
jimmytaker
 
Posts: 18
Joined: Fri Dec 23, 2016 11:04 pm

Re: QxEntityEditor 1.2.1 known issues

Postby jimmytaker » Thu Jan 12, 2017 3:11 pm

Hi,
found 2 more issues - both with relationships between tables.

In my case I have this problem with 1-N relationships. Have not tested with other types.

1. Double clicking on a relationship does not always open it. After the double click, the relationship window flashes for a sec and then the window disappears and the message "Please select a relationship to display parameters" appears. This issue cannot be always reproduced and it appears that scrolling up and down the area and then double clicking again, I can eventually open the relationship editor. Let me suggest here, that you could make it so that you can enter the relationship editor by clicking somewhere on the relationship in the table of the table editor. Not only by double clicking on the line in graph.

2. Writing a description in the relationship editor does not always get saved. Sometimes after you open it again right after saving, the description is gone. Also sometimes even if the relationship editor shows the description, when the C++ classes are generated, the description is missing. To fix this, I need to change the description a few times, re-save it every time, and eventually it gets saved correctly and is present in the generated class. The issue cannot always be reproduced, but more often than not, I have the problem.
jimmytaker
 
Posts: 18
Joined: Fri Dec 23, 2016 11:04 pm

Re: QxEntityEditor 1.2.1 known issues

Postby qxorm » Thu Jan 12, 2017 7:49 pm

Thx, I will try to reproduce your issues to fix them.
qxorm
Site Admin
 
Posts: 406
Joined: Mon Apr 12, 2010 7:45 am

Re: QxEntityEditor 1.2.1 known issues

Postby qxorm » Sun Jun 04, 2017 6:59 pm

- Column names are not escaped in the mysql generated .sql, so having an sql word such as "order" as a column name does not work.

- Would be nice if the projects in recent project had full path in addition to the project name, so that same name projects can be distinguished. Same applies for the window title bar.

- The problem is that the name of the relationship name should be the same in both. Or it does not get found, because the collection contains the other name. I have changed the name of the relationship in the QxEntityEditor.

- Double clicking on a relationship does not always open it.

All these issues are fixed in QxEntityEditor 1.2.2 : viewtopic.php?f=7&t=766
qxorm
Site Admin
 
Posts: 406
Joined: Mon Apr 12, 2010 7:45 am


Return to QxEntityEditor - Help

Who is online

Users browsing this forum: No registered users and 1 guest

cron