Re: ``models.BooleanField`` fields default to ``False`` when missing from fixtures

2012-09-24 Thread Yo-Yo Ma
The gremlin example was just a light-hearted attempt at justifying the claim of "data corruption", in response to Florian, but I really only brought up this issue because it surprised me (nothing in the docs). I would suggest a docs update to let developers know that if a default isn't set,

Re: ``models.BooleanField`` fields default to ``False`` when missing from fixtures

2012-09-24 Thread Russell Keith-Magee
On Tue, Sep 25, 2012 at 8:00 AM, Yo-Yo Ma wrote: > Developer of a pet shop software adds: > > feed_before_midnight = models.BooleanField() > > because they're planning on carrying baby gremlins... forgets to update the > zoological XML feed importer to use the

Re: ``models.BooleanField`` fields default to ``False`` when missing from fixtures

2012-09-24 Thread Yo-Yo Ma
Developer of a pet shop software adds: feed_before_midnight = models.BooleanField() because they're planning on carrying baby gremlins... forgets to update the zoological XML feed importer to use the "feed_before_midnight" value, and the rest is history :) On Monday, September 24, 2012

Re: ``models.BooleanField`` fields default to ``False`` when missing from fixtures

2012-09-24 Thread Florian Apolloner
On Monday, September 24, 2012 3:07:37 PM UTC+2, Yo-Yo Ma wrote: > > Yep, that looks like it. IMHO, this is a bug that should be fixed without > delay, as it breaks a cardinal rule for Pythonistas, and could even lead to > a "data corruption" situation, if a dev was to add a boolean field and >

Re: ``models.BooleanField`` fields default to ``False`` when missing from fixtures

2012-09-24 Thread Yo-Yo Ma
Yep, that looks like it. IMHO, this is a bug that should be fixed without delay, as it breaks a cardinal rule for Pythonistas, and could even lead to a "data corruption" situation, if a dev was to add a boolean field and forget to update a form or fixture, or both. On Monday, September 24,

``models.BooleanField`` fields default to ``False`` when missing from fixtures

2012-09-23 Thread Yo-Yo Ma
This may be the intended behavior, but I couldn't find docs on it. My recommendation would defer to "The Zen of Python" In the face of ambiguity, refuse the temptation to guess. I would rather see the typical IntegrityError: Problem installing fixture... -- You received this message