-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Problem with running migrations #59
Comments
Why are you using the |
Oh, are you getting this error if you are running built-in migrations like reminders? I will add a string method to the blueprint class that does nothing to solve this :) |
I updated the schema builder to support "fluent" schema building. |
This was referenced Nov 26, 2018
3 tasks
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I've noticed a problem that's come about recently (possibly as a result of updating the Laravel framework) where Laravel falls down because it's trying to call method "string()" when creating a migration table in the target database migrations table.
When running the migrations, it throws this error:
So it appears to be trying to call "string()" on the Jenssegers\Mongodb\Schema\Blueprint class (which doesn't currently support string).
Is there a solution for this? I can hardly see it being worth it to implement a string method just for a workaround with the Laravel framework.
The text was updated successfully, but these errors were encountered: