LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase (MySQL)
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
The bug with wrong order for creation tables with the many-to-many associations via the CreateDatabase() method is fixed. The fix will be included in the next build of LinqConnect. We will inform you when it is available for download.
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
New build of LinqConnect 4.4.403 is available for download now!
It can be downloaded from http://www.devart.com/linqconnect/download.html (trial version) or from Registered Users' Area (for users with active subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?f=31&t=28602.
It can be downloaded from http://www.devart.com/linqconnect/download.html (trial version) or from Registered Users' Area (for users with active subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?f=31&t=28602.
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
OK. Wrong order for creation tables is fix. Thanks.
But already have any problem:
1) Default value; (Critical issue)
2) Foreign key name;
3) Action for constraints. (Critical issue)
Please see to image.
Full link: http://s5.hostingkartinok.com/uploads/i ... 89416a.png
But already have any problem:
1) Default value; (Critical issue)
2) Foreign key name;
3) Action for constraints. (Critical issue)
Please see to image.
Full link: http://s5.hostingkartinok.com/uploads/i ... 89416a.png
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
Thank you for the response.
Please refer to: http://dev.mysql.com/doc/refman/5.0/en/ ... -keys.html
This issue has not been fixed yet. We will inform you when the corresponding build with the fix is available.1) Default value; (Critical issue)
The issue with the difference in generating foreign key names between Entity Developer and CreateDatabase() method has a low priority. We will definitely contact you as soon as any results are available.2) Foreign key name;
All delete rules, except "NO ACTION", are generated for the associations via the CreateDatabase() method. The "NO ACTION" delete rule is not generated due to the fact that in MySQL it is equivalent to "RESTRICT" - the MySQL Server rejects the delete or update operation for the parent table if there is a related foreign key value in the referenced table. If the delete rule is not specified, the default action is always set to "RESTRICT".3) Action for constraints. (Critical issue)
Please refer to: http://dev.mysql.com/doc/refman/5.0/en/ ... -keys.html
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
1) Ok, waiting. Sometimes it is very critical.
2) Yes this is low priority.
3) Yes, indeed. But still I would like to make it the same way.
2) Yes this is low priority.
3) Yes, indeed. But still I would like to make it the same way.
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
All the same, this problem is very critical.2) Foreign key name;
I can not prepare a script to update the database, because I do not know foreign key name.
This is a very serious problem.
Very much I ask as soon as possible to fix all three errors.
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
The behaviour is changed: now the CreateDatabase() method uses the same algorithm for naming foreign keys as in Entity Developer. We will inform you when the corresponding build of LinqConnect is available for download.
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
Well, finally!
Only foreign keys?
But what about the default values for fields, comments, action for constraints...?
Or all the same now, one algorithm?
One can try to build 4.4.428?
Only foreign keys?
But what about the default values for fields, comments, action for constraints...?
Or all the same now, one algorithm?
One can try to build 4.4.428?
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
The fix related to the foreign keys will be available in the next build of LinqConnect.
We will contact you as soon as any news are available.
We can't tell any timeframe for fixing this issue at the moment.1) Default value; (Critical issue)
This behaviour will be changed in one of the next public builds of LinqConnect.3) Action for constraints. (Critical issue)
We will contact you as soon as any news are available.
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
Ok, really looking forward to.
Why not use a single code and logic to create a database both in the Entity Developer? In order to avoid the problem altogether.
There is a possibility that in the future will be constantly revealed differences.
Why not use a single code and logic to create a database both in the Entity Developer? In order to avoid the problem altogether.
There is a possibility that in the future will be constantly revealed differences.
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
Due to incorrect naming foreign key problem is even more complicated. The process of updating such databases has become a horror.
Entity Developer when updating the database from the model does not account for incorrect names, and does not change them for new ones.
Very much I ask take into account this and to do this he compared the names and corrected on the right.
Entity Developer when updating the database from the model does not account for incorrect names, and does not change them for new ones.
Very much I ask take into account this and to do this he compared the names and corrected on the right.
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
Entity Developer shouldn't detect the changes in foreign key names. The foreign key names are irrelevant for the ORM, the main thing is their structure. Moreover, starting from the next build, which we plan to release this week, some changes in LinqConnect runtime regarding working with foreign key names will be available.Entity Developer when updating the database from the model does not account for incorrect names, and does not change them for new ones.
Also, you can use "Recreate Database Tables" option to recreate the database tables so that the foreign key names were correct.
We have changed this behavior. The fix will be included in the next public build of LinqConnect.3) Action for constraints. (Critical issue)
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
New build of LinqConnect 4.4.438 is available!
It can be downloaded from http://www.devart.com/linqconnect/download.html (trial version) or from Registered Users' Area (for users with active subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?f=31&t=28939.
It can be downloaded from http://www.devart.com/linqconnect/download.html (trial version) or from Registered Users' Area (for users with active subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?f=31&t=28939.
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
LinqConnect Professional Version 4.4.438 (13-Feb-2014)
But already have any problem:
1) Foreign keys name different; (Critical issue)
2) Wrong field used in relations. Are mixed up!; (Critical issue)
3) Don`t set default value; (Critical issue)
4) Don`t add comments.
5) Action for constraints.
Please see to image.
1) Very critical.
Full link
2) No critical.
Full link
LinqConnect Professional Version 4.4.438 (13-Feb-2014) - Problems.zip (256.1 КБ) - http://rghost.ru/52440842
(archive include, full backup scripts, small for diff, images and info)
For me, these issues are very important, they do not allow updating client databases that were created from the program using the command CreateDatabase ()!
Very much I ask fix as soon as possible.
But already have any problem:
1) Foreign keys name different; (Critical issue)
2) Wrong field used in relations. Are mixed up!; (Critical issue)
3) Don`t set default value; (Critical issue)
4) Don`t add comments.
5) Action for constraints.
Please see to image.
1) Very critical.
Full link
2) No critical.
Full link
LinqConnect Professional Version 4.4.438 (13-Feb-2014) - Problems.zip (256.1 КБ) - http://rghost.ru/52440842
(archive include, full backup scripts, small for diff, images and info)
For me, these issues are very important, they do not allow updating client databases that were created from the program using the command CreateDatabase ()!
Very much I ask fix as soon as possible.
Re: LinqConnect Professional Version 4.4.374 (14-Nov-2013) - Many problems with CreatDatabase
Thank you for the response.
We have reproduced the issue with foreign keys for many-to-many associations. We will inform you when these issues are fixed.1) Foreign keys name different; (Critical issue)
2) Wrong field used in relations. Are mixed up!; (Critical issue)
5) Action for constraints.
We can't tell any timeframe for fixing these issues at the moment.4) Don`t add comments.
3) Don`t set default value; (Critical issue)