-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSSQL - Diff generates wrong syntax on ALTER TABLE #1294
Comments
Same problem happends with "ALTER TABLE x ADD column_a;" |
atompulse
added a commit
to atompulse/Propel2
that referenced
this issue
Aug 28, 2017
propelorm#1294 propelorm#1343 Solved: - size checking issue - default values issue - foreign keys actions (on delete/on update) Remaining: - sql syntax for alter table
atompulse
added a commit
to atompulse/Propel2
that referenced
this issue
Aug 29, 2017
propelorm#1294 propelorm#1343 Solved: - column renaming
atompulse
added a commit
to atompulse/Propel2
that referenced
this issue
Aug 31, 2017
propelorm#1294 propelorm#1343 Solved: - column changing (structure)
atompulse
added a commit
to atompulse/Propel2
that referenced
this issue
Nov 22, 2017
propelorm#1294 propelorm#1343 Solved: - size checking issue - default values issue - foreign keys actions (on delete/on update) Remaining: - sql syntax for alter table
atompulse
added a commit
to atompulse/Propel2
that referenced
this issue
Nov 22, 2017
propelorm#1294 propelorm#1343 Solved: - column renaming
atompulse
added a commit
to atompulse/Propel2
that referenced
this issue
Nov 22, 2017
propelorm#1294 propelorm#1343 Solved: - column changing (structure)
Closing in favor of the other ticket with more details. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you change a type in your schema.xml and the column has to be modified, propel generates wrong syntax on the update statements. This happens on any table/column if you change their type afterwards.
Generated statement:
Exception of the executed statement:
Correct Syntax would look like this:
You can not modify multiple columns at once with MSSQL.
The text was updated successfully, but these errors were encountered: