mysql ignoring :length option while migrating
Reported by Uros Zekar | March 24th, 2009 @ 11:08 PM
The migration for mySQL creates varchar(50) for all "String"
columns. It results in the error like this when it finds a message
or author that exceeds 50 chars: (mysql_errno=1406,
sql_state=22001) Data too long for column 'message' at row 1 Query:
UPDATE integrity_commits SET message =
'Build distributables under pkg/ instead of dist/ (per blake's
request)', updated_at = '2009-03-24 14:28:48',
author = 'Ryan Tomayko rtomayko@gmail.com',
committed_at = '2009-03-24 01:47:24' WHERE
(id = 1)
I resized the message and author manually to varchar(255): ALTER TABLE integrity_commits MODIFY message varchar(255), MODIFY author varchar(255);
Comments and changes to this ticket
-
Simon Rozet March 26th, 2009 @ 01:03 PM
- Tag set to “dm, external, mysql”
- Milestone cleared.
- State changed from “new” to “open”
- Assigned user changed from “ronin-278 (at lighthouseapp)” to “Simon Rozet”
-
-
Simon Rozet June 11th, 2009 @ 10:38 AM
- State changed from “invalid” to “dupe”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Automated continuous integration server that doesn't suck.
Simon Rozet
