On Wed, Jul 29, 2015 at 11:42 AM, Podrigal, Aron <ar...@guaranteedplus.com> wrote:
> Hi Loic, > > Agree with having a db_default kwarg. > > I am not using multiple databases so no experiance with db routers. So how > would should we handle routing between different databases when the > db_default value is not compatible with that backend? for example > Model.save(using='mysql_db') should we than use the Field.default to > generate the default value (which is not how it works today, that the > default is computed at instance creation). I would prefer in such a case to > rely on the database to handle the situation by omitting that field from > the columns list, so mysql for example would set a non nullable varchar > column to an empty string, where with other databases it would cause an > IntegrityError exception. and that db_default and default kwargs cannot be > used togethor. > If db_default is defined for a field, then it should always be used. If the db_default is invalid for the configured backend, then it will and should break. We shouldn't automatically change db_default to a regular default or do any other magic. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAGdCwBsHa%2BGXJSB6fay%3DbM%2B-3qV0y5oSuDNd4m05QM1PPdfKrw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
