It isn't always possible to transform arbitrary Python defaults
(particularly callables) into SQL.
A search query would help you answer a question like this. I typed
"django database column defaults site:code.djangoproject.com" into Google
and found
https://code.djangoproject.com/ticket/470 amon
Out of curiosity, why isn't this added as part of the column definition?
Isn't it better to enforce the default at the DB layer? Or is it to account
for differences across database types? (This trips me up a lot because we
have a lot of different apps/processes which have to touch the database a
Hello Tim,
Considering that there’s no evidence of anyone using the feature, that it
doesn’t work well in all circumstances, that we have an alternative which works
better and has no downsides (considering the new policy on dependencies), I
think that’s reasonable.
I’m afraid we’ll get a coupl
