strip schema name from ADD CONSTRAINT / CREATE INDEX #48
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pg tablenames may have a schema prefix. This leads to invalid ADD
CONSTRAINT / CREATE INDEX statments being generated by ->deploy(),
since constraint and index names may not have a period in them. This
patch strips the schema part from the table name when constructing
unique index and constraint names. The fix was taken from
ribasushi's email to the mailing list:
http://lists.scsys.co.uk/pipermail/dbix-class/2013-February/011141.html