This project is archived and is in readonly mode.
Don't add DEFAULT NULL to column definitions
Reported by Nick Sieger | June 5th, 2008 @ 02:27 AM
Commit 10ef65a3b054270ed3d458ec8eb7c2b9a3e638f7 introduced a strange side-effect to create table definitions. It causes DEFAULT NULL to be included all the time. Some databases are ok with this, but some are not. Example:
`title` varchar(255) DEFAULT NULL NULL
Patch attached to omit passing :default option to #add_column_options! if it is nil.
Comments and changes to this ticket
-
Repository July 14th, 2008 @ 04:14 PM
- Tag set to “activerecord, migrations, tested”
(from [30370227890dc950f1544b7b1040aa75e505f877]) Fixed that create database statements would always include "DEFAULT NULL" (Nick Sieger) [#334 status:committed]
-
DHH July 14th, 2008 @ 04:36 PM
- State changed from “new” to “committed”
-
Repository July 15th, 2008 @ 11:56 PM
(from [275c3ab2a7aac60ad30ab027d1f0b1f041fb016d]) Fixed that create database statements would always include "DEFAULT NULL" (Nick Sieger) [#334 status:committed]
Conflicts:
activerecord/CHANGELOG
-
-
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>
DHH
Jeremy Kemper
Nick Sieger
Repository
Ryan Bigg