Setting database default values in migrations (postgres)

Hey all, I'm interested in getting database migrations to support setting database-level default values. I've heard talk of this being a hotly contested issue in the past, but I haven't been able to find the actual conversations, so far this

Re: Setting database default values in migrations (postgres)

es the very common > default=datetime.datetime.now). Obviously all calls through Django will > still work as intended, but other database users will have entirely the > wrong value in that field whenever they insert rows but no errors to tell > them about it (and if you don'

Re: Setting database default values in migrations (postgres)

want some way to declare what defaults > to keep. (South actually used to have this with a keep_default option on > the add_column method but it was kind of unmaintained) > > Andrew > > On Thu, Oct 30, 2014 at 1:45 PM, Peter Coles > wrote: > >> Thanks for the quick