-
Notifications
You must be signed in to change notification settings - Fork 41
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
Error on migration containing references(...)
field type
#61
Comments
@Qqwy I think we should warn instead or ignoring there, so that developer knows what is actually happening. PR is welcome :) |
Turns out the reason for this is that Ecto until 2.2 required you to use an atom as table name in references (So |
The README states:
I just tried to migrate a Postgres-app over to Ecto_Mnesia, and it was unable to run my migrations because I had
references("table_name")
fields in there. Since this is also 'just a type', I think better behaviour would be to ignore the result from this as well.The text was updated successfully, but these errors were encountered: