I'm sorry, but generating unique constraint names from the table name is a bad idea:
You might be aware that some databases (read: Oracle) have a very low limit on identifier length (30 chars, see ORA-00972). If the table name itself is already at that limit, your solution will fail.
I really don't understand why you want to create the unique constraints in 'alter table' statements. There was nothing wrong with creating them in the column/table definition, while using 'alter table' has all sorts of new problems.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
I'm sorry, but generating unique constraint names from the table name is a bad idea:
You might be aware that some databases (read: Oracle) have a very low limit on identifier length (30 chars, see ORA-00972). If the table name itself is already at that limit, your solution will fail.
I really don't understand why you want to create the unique constraints in 'alter table' statements. There was nothing wrong with creating them in the column/table definition, while using 'alter table' has all sorts of new problems.