Hi, On Tuesday, March 5, 2013 8:35:07 PM UTC+1, Michael Manfre wrote: > > The current discussion about "Switch to database-level autocommit" ( > http://bit.ly/ZlVERI) reminded me of a past discussion regarding moving > the database backends out of the core. I don't remember exactly where I > heard the discussion, but I'd like to revive it. My proposal is to move all > database backends out of Django, except for an sqlite reference > implementation.
While I agree that moving database adapters out of core has some merit, I don't think that having sqlite as a reference implementation is a good idea: For one some features are somewhat hacky in sqlite (and people tend to copy from reference implementations, so it should be as clean as possible) and it's lack of data validation makes it imo a nogo. The reference implementation should imo also have strong support for GIS, which is somewhat okay on sqlite but quite hard to install. So if we were to do that I'd either vote for postgres or supporting postgres and sqlite inside of core (the later solely for fast tests). Cheers, Florian -- 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 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
