-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
migration:refresh command not working properly #81
Comments
Would you like to share the screenshot of |
Yup identified bug. I changed the behavior of pluck in this d8603d1 commit. Will fix it and rename |
Great, thank you! |
Want to give it a try from by installing it from GH? npm i --save https://github.com/adonisjs/adonis-lucid.git\#develop |
Yup, tried it ... all works perfectly now, thanks again! |
Hello, Is there going to be an official fix on the framework? |
I am still having this issue even with Error: create table `users` (`id` int unsigned not null auto_increment primary key, `deleted_at` datetime null) - ER_TABLE_EXISTS_ERROR: Table 'users' already exists |
Hey @LaloHao 👋🏼 It may be an issue with a desync of the |
Hi @RomainLanz , i do think thats my problem, this is my
I just executed Error: create table `transactions` (`id` int unsigned not null auto_increment primary key, `amount` int, `description` varchar(255), `created_at` datetime, `updated_at` datetime, `deleted_at` datetime null) - ER_TABLE_EXISTS_ERROR: Table 'transactions' already exists If i just drop manually the tables |
change in pluck signature seems to be producing breaking changes, which is not ideal and must be avoided. Renamed the method to pluckAll Closes #81
Having the same issue with mysql
|
Hi,
Running the
migration:refresh
command always logs the following error:ER_TABLE_EXISTS_ERROR: Table 'deploys' already exists
Here is the related migration class:
It seems like the
down
method is never called. I've tried this with different drivers (sqlite3, mysql, mysql2) and am having the same problem.I'm not sure if this is related, but running the
migration:reset
command always logs:Already at the latest batch.
although it should actually be callingdown
on all migrations if I understand that correctly.If it helps here is the output of
migration:status
:Thanks for all the hard work, I'm just working my way into the framework but am really enjoying using it so far!
The text was updated successfully, but these errors were encountered: