On Fri, 2006-07-07 at 14:38 +0200, Geert Vanderkelen wrote: > Malcolm Tredinnick wrote:
> > I would add, for most projects, it's not a really clear cut case. Django > > hides the SQL oddities for you, so there's not going to much difference > > there (using MySQL 5 with transaction support is kind of assumed here, > > although even that's not clear cut in some cases). > > MySQL supports transcations since 3.23 (which is ages ago). James Bennett > did mention it, but I'll repeat: you need to use InnoDB storage engine to > get transactional support. My main reason for mentioning version 5 was mainly to avoid thing the limitations on the length of VARCHAR fields (which could only be up to 255 chars prior to MySQL 5.0). This has bitten some people using CharFields in Django and they had to switch to TextFields, which present themselves slightly differently. I wasn't intending to imply the verison number was related to transactional availability. Apologies for any confusion. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
