On 4/2/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > Its a question of standards. Postgres works at trying to comply with > SQL standards - which means that migration to other standards > compliant databases is easier - but then django masks all that. > Secondly postgres is ACID compliant - but then django doesnt do > ACID, so is now not suitable for mission critical applications. But > when it does, i feel postgres would be the way to go.
Sort of OT, but MySQL with InnoDB tables claims to give ACID compliant transaction support. And Django now has transactions... -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
