We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
change_table... t.enum fieldname ...
error type "string" DOES NOT EXIST.
didn't catch this in development, apparently sqlite doesn't mind it, but PostgreSQL did not like it when i pushed to staging.
The text was updated successfully, but these errors were encountered:
Just use string then.
J
On Tue, Sep 13, 2011 at 2:36 PM, fringd < [email protected]>wrote:
change_table... t.enum fieldname ... error type "string" DOES NOT EXIST. didn't catch this in development, apparently sqlite doesn't mind it, but PostgreSQL did not like it when i pushed to staging. Reply to this email directly or view it on GitHub: #33
Reply to this email directly or view it on GitHub: #33
Sorry, something went wrong.
OK.. works fine... fix readme b4 closing? On Sep 13, 2011 6:55 PM, "jeffp" < [email protected]> wrote:
Just use string then. J On Tue, Sep 13, 2011 at 2:36 PM, fringd < [email protected]>wrote: change_table... t.enum fieldname ... error type "string" DOES NOT EXIST. didn't catch this in development, apparently sqlite doesn't mind it, but PostgreSQL did not like it when i pushed to staging. Reply to this email directly or view it on GitHub: #33 Reply to this email directly or view it on GitHub: #33 (comment)
Reply to this email directly or view it on GitHub:
#33 (comment)
See also #43
No branches or pull requests
change_table...
t.enum fieldname
...
error type "string" DOES NOT EXIST.
didn't catch this in development, apparently sqlite doesn't mind it, but PostgreSQL did not like it when i pushed to staging.
The text was updated successfully, but these errors were encountered: