Hi, On Wednesday, March 6, 2013 3:32:45 PM UTC+1, Michael Manfre wrote: > > The lack of data validation is definitely a nogo for production sites, but > imo sqlite in production is also a nogo. >
Right, but shipping Django with a non production db might send interesting signals to endusers ;) 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). >> > > . I've never tried to install GIS for sqlite, but is the difficulty due to > lack of documentation or just sheer number of steps? > Well it's not to bad, we did document it after all, but it usually requires recompiling sqlite and pysqlite (most importantly you can't pull it from your distros repos). Regards, 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.
