[dm-migrations] don't auto_upgrade! not nullable columns with no explicitly given default value
Reported by Martin Gamsjaeger (snusnu) | August 20th, 2009 @ 12:54 AM
i was just wondering if it's maybe "safer" to issue a warning and don't auto_upgrade a not nullable column that has no explicitly given default value .. it can be argued that the developer should be knowing all that, but well ...
i think the defaults that the storage engine creates if no explicit ones were given will almost always be useless (wrong) .. if one overlooks something, then at least the tables (possibly production since it's auto_upgrade) don't get stuffed with trashdata
Comments and changes to this ticket
-
Martin Gamsjaeger (snusnu) August 20th, 2009 @ 06:31 PM
- State changed from “unconfirmed” to “suggestion”
-
Piotr Solnica (solnic) May 17th, 2011 @ 02:33 AM
- Tag changed from “suggestion” to “dm-migrations, suggestion”
- Milestone order changed from “0” to “0”
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 »
Martin Gamsjaeger (snusnu)
Piotr Solnica (solnic)