Devart Forums

Since the last release (4.2.129) the database wizards appear to be broken.

The Update Database wizard is dropping every single many-to-many link-table from my schema, and refuses to recreate them.

Generating a new database schema doesn't work either - it's leaving out all the many-to-many link-tables from the generated schema, they don't even appear as options on the first page of the wizard dialog.

At first I thought this was another problem with the upgrade process from the previous version file format, but even for a newly added many-to-many relationship, the link-table doesn't even appear as an option in the Update Database wizard...

Another bug in the Update Database wizard: almost every column shows up as "changed" - but when you review the change, it turns out all that changed was the Comment on the property; no change to the columns as such.

Since comments aren't output and added to the schema columns (which by the way is possible via extended column properties in SQL Server), any property/column with a comment on it will show up as changed, every time you run the wizard.

As a result, redundant ALTER TABLE statements are generated on every run.

mindplay wrote:The Update Database wizard is dropping every single many-to-many link-table from my schema, and refuses to recreate them.

We have reproduced the issue. We will post here when it is fixed.

mindplay wrote:Another bug in the Update Database wizard: almost every column shows up as "changed" - but when you review the change, it turns out all that changed was the Comment on the property; no change to the columns as such.

The Summary attribute of the Documentation property corresponds to the Comment attribute of the column in the database. So, changes in Summary make its table marked "Changed" in Update Database From Model. We have reproduced the bug with the generated SQL when a comment is added/changed in Summary. We will notify you when the issue is fixed.

Shalex wrote:The Summary attribute of the Documentation property corresponds to the Comment attribute of the column in the database. So, changes in Summary make its table marked "Changed" in Update Database From Model. We have reproduced the bug with the generated SQL when a comment is added/changed in Summary. We will notify you when the issue is fixed.

Just to make sure we're on the same page - having the Summary written to the schema would be great, but it doesn't actually do that.

What I'm saying is, the Summary never gets written to the database in the first place. So this problem occurs, not when I add or change the Summary, but for any property that has a Summary, every time - regardless of whether I make changes.

We have reproduced the bug with the generated SQL when a comment is added/changed in Summary (the changes are not propagated to the database). We will notify you when the issue is fixed.

The bug with setting comments for columns and tables in database is fixed. We will post here when the corresponding build of Entity Developer is available for download.

The bug with generating SQL for creating a link-table of many-to-many association is fixed. We will post here when the corresponding build of Entity Developer is available for download.

What's the forecast for a release? We need to deploy this application soon, and currently have no effective way to do schema migrations...

We are planning to release the new build of Entity Developer in the beginning of the next week. We will post here when it is available for download.

Many-to-many link-tables are now generated and updated correctly.