-
-
Notifications
You must be signed in to change notification settings - Fork 725
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
postgresql constraints all get the same name #307
Comments
my solution, maybe you can think of something similar ....;) |
deal with default value: <xsl:if test="default and not ( default = 'NULL' or default = "'NULL'" )"> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems postgresql schemas get the same name for all constraints for a table (which obviously won't work)
I tried setting up a simple table with a
id
auto_increment primary key and acode
text column that's unique:This is what it generated:
Notice how they are both named
test_pkey
. This does not work.If I give the constraints specific names, it still doesn't change this behavior.
The text was updated successfully, but these errors were encountered: