This repository has been archived by the owner on Apr 17, 2018. It is now read-only.
Allowing bytea columns to migrate by ignoring length #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
solnic
added a commit
that referenced
this pull request
Oct 9, 2011
Allowing bytea columns to migrate by ignoring length
|
@miegs3 thanks! |
|
will that see a release one day ? kind of difficult to monkey patch this to get datamapper migration working on heroku: http://stackoverflow.com/questions/10154641/removing-limit-from-binary-column-for-postgresql-in-datamapper |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I found that I was unable to migrate into postgres when defining a binary property because the column was being defined with the default length.
Currently TEXT, CLOB and NVARCHAR were ignoring the length so I've added bytea to this list.