[BangPypers] Fwd: do I need to run syncdb when I change the default value in a field of a model?

Venkatraman S venkat83 at gmail.com
Mon Apr 7 08:56:17 CEST 2014

FYI. I think this was a good design decision; I never realized the
importance of this feature until I stumbled on something interesting by
sheer serendipity.


---------- Forwarded message ----------
From: Russell Keith-Magee
Date: Fri, Mar 21, 2014 at 5:43 AM
Subject: Re: do I need to run syncdb when I change the default value in a
field of a model?
To: Django Users <django-users at googlegroups.com>

On Thu, Mar 20, 2014 at 6:50 PM, Venkatraman S <> wrote:

> On Sat, Mar 15, 2014 at 7:11 AM, Russell Keith-Magee <> wrote:
>> On Sat, Mar 15, 2014 at 7:19 AM, Jonathan Baker <> wrote:
>>> Does that mean that the default="" functionality is implemented by the
>>> ORM, instead of in the database layer?
>>> This is correct - Django's "default" argument is an API level default,
>> not a database level default.
> @Russ, any specific reasons for this choice?

Honestly - not a clue. It was like that when I got here, so the reasons are
probably lost in the depths of time. :-)

Trying to reverse engineer the decision, the most likely reason is that
Django has allowed callable defaults; if you define a callable in your
Django model as a default, there's no way to pass this down to the database
(or, at least, not an easy way).

Russ Magee %-)

You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to django-users+unsubscribe at googlegroups.com.
To post to this group, send email to django-users at googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit

For more options, visit https://groups.google.com/d/optout.

More information about the BangPypers mailing list