Yes, this means that people with MySQL 3/4 databases will need to
upgrade or choose another database. But why should we spend so much
time and effort writing, testing, and debugging a reimplementation of
referential integrity in Django simply to support those who come to
Django asking "Hey, I've got this nail; how do I use this bratwurst as
a hammer?". Django is a complex enough without complicating the
problem by reimplementing half the features of a database to support
those in the community that can't/won't upgrade.
Hi, I appreciate your work but if it works by break it? I am thinking a good percentage of users will be using shared hosting etc to deploy their application, and they have very little control over the version of SQL server. [ object.delete() for object in get_list()] works, if its too slow, use custom sql [work on making it easy if it is not]. Delete is an edge case anyways.
--
Amit Upadhyay
Blog: http://www.rootshell.be/~upadhyay
+91-9867-359-701
