-
Notifications
You must be signed in to change notification settings - Fork 595
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
Laravel 5.4 migration problem #249
Comments
I get the same error. :\ |
I get the same issue also. |
same errore |
Have the same issue please help |
As said in #250, should be fixed now. |
Yes, this error got fixed, but now im getting on newest Laravel and newest xampp and easyphp this error:
|
Seems to be related to this issue: |
I was able to get pass this, but then i get error in last migration:
So i did this migration manually by changing sql to: alter table |
It's probably related to the changes made to MySQL new uft8 charset. |
Posted and answered it on StackOverflow: This is due to sql mode [STRICT_TRANS_TABLES][1], so you have three options:
Which will disable all those sql modes:
So, we should investigate it and probably do nr 1) on Tracker, right? |
Is this the same issue ? I am getting this output when trying to migrate. and also I am using,
Any idea what went wrong ? |
Same as @nipun5perera. Tried it again, fresh pull of the latest Tracker. Set strict to false. Still getting the 42000 error. |
Any luck trying to solve this ? |
I did edit create_tracker_agents_table.php and changed ,
to
and then added
so my create would look like this,
and then edited fix_agent_name.php and changed
to
for me this solved that key length problem and everything migrated successfully. |
Laravel's default $table->timestamps() migration method calls nullable() on created_at and updated_at, so why aren't we doing this when calling timestamp('created_at')->index() ? Why not do this in each of the migrations:
|
Not sure if this is related, but I am having issues with migrating. When I run |
I just removed the 'fix_agent_name' migration and everything worked as intented |
Thanxs for update,
Also have already done the same adn everything is alright now
…On Wed, Mar 22, 2017 at 8:22 AM, Austin Teague ***@***.***> wrote:
I just removed the 'fix_agent_name' migration and everything worked as
intented
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#249 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATRlDcZX5akn8OFEiqLFYfjSLlEB8y3mks5roLARgaJpZM4MBj1U>
.
|
Solved it.
to
|
Or you could change 2017_01_31_311101_fix_agent_name.php |
I used database prefix which was an issue. Solution is replacing
with
|
When installing tracker on fresh Laravel 5.4 i get this error:
The text was updated successfully, but these errors were encountered: