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...
Update database wizard is broken
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.
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.
We have reproduced the issue. We will post here when it is fixed.mindplay wrote:The Update Database wizard is dropping every single many-to-many link-table from my schema, and refuses to recreate them.
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.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.
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.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.
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.