-
-
Notifications
You must be signed in to change notification settings - Fork 553
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
fix(mssql): only last column in foreign key definition kept #1594
base: master
Are you sure you want to change the base?
Conversation
Very interesting and useful work: in mssql-schema.lisp I had a problem with parentheses... so no compilation
|
It seems like a compilation error was introduced in this PR. Can you see about fixing it before merge?
|
Yes, will fix it later today. Fixed it in another PR, but forgot to cherry-pick the fix here. |
On my system, this Debian Autopkgtest/debian-build works..
|
For SQL Server, when copying foreign key definitions with multiple columns, only the last of N columns is taken over.
The original code tried to aggregate columns in-place, but it seems that some part of the code does not retrieve the original, but rather creates a new list/foreign key object.
Adjust the SQL query, to do the column name aggregation. Then we can avoid having the lisp code to in-place update magic.
(Similar to how it's done in the other DB kind code.)
(I suppose there's great potential to unify the code.)