-
Notifications
You must be signed in to change notification settings - Fork 178
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
Spatial index detection in schema #198
Comments
Did you try to create a new database and run all your migrations and then running again the schema update --dump-sql? |
I've just tried, same thing happening. |
I have the same issue here. Was this ever fixed or is there any workaround? |
Hi @echantigny, if you still have the issue with feel free to submit a PR if you find the issue. |
For anyone seeing this late, the solution for me was: I hope this helps out someone. |
Each time I execute a schema update with --dump-sql SQL option, it gives me:
Even if I execute it with --force option, it always want to drop and recreate the index (with the same name).
I don't know what it's worth, but I remember I had this bug a year ago. It was not present anymore, and reappared after I did a composer update (doctrine/orm upgraded from 2.6.2 to 2.6.3).
The text was updated successfully, but these errors were encountered: