This project is archived and is in readonly mode.
Mysql text/blob column peculiarity
Reported by Frederick Cheung | September 14th, 2008 @ 12:11 PM
Mysql has some slightly peculiar behaviour when it comes to defaults and not null blob/text columns: they cannot have a default and show fields reports they have a default of null , but behave as if they have an implicit default of ''. The attached patch deals with this
Comments and changes to this ticket
-
Michael Koziarski September 14th, 2008 @ 04:57 PM
- Assigned user set to Jeremy Kemper
- Milestone cleared.
-
Repository September 15th, 2008 @ 01:11 AM
- State changed from new to committed
(from [d51a39ff500d94ea4a81fbc22f0d1c540e83f4e1]) Deal with MySQL's quirky handling of defaults and blob/text columns
[#1043 state:committed]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net http://github.com/rails/rails/co...
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Attachments
Tags
Referenced by
- 1043 Mysql text/blob column peculiarity [#1043 state:committed]