On Saturday 01 March 2014 19:07:08 Aymeric Augustin wrote: > On 1 mars 2014, at 09:14, Martin Matusiak <[email protected]> wrote: > > Now in the case of sqlite, which is very permissive, it will happily > > accept values like 1 and {} and store them as "1" and "{}" (wtf) > > respectively. So if I'm running my tests against sqlite I won't even > > know that this will bite me in production. > > You should never, ever, for any reason, use a different database in > development, test and production. It's a bad idea. It doesn't work. > ... except when you're developing for more than one database. Then you're allowed to use just one in development, but you should have CI covering all your targets for testing. Separating testing from production really has no excuse, AFAICT.
Shai. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. 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/201403020949.35736.shai%40platonix.com. For more options, visit https://groups.google.com/groups/opt_out.
