Hugo/Georg is exactly correct.
I'm sure there are many very large websites using Django, but from what
I see many are newspaper-style (many reads, few if any writes except by
the admins). I'd be curious how may sites are doing dynamic updates by
many concurrent users? In a read-only / content / presentation oriented
site (as Hugo calls them) you won't run into this problem.
The banking example above or my example across two machines is exactly
the sort of problem that Django doesn't support.
"Of *course* you'd expect that obj2.data != obj1.data"
No ... I'd *absolutely* expect obj2.data == obj1.data or it should
throw an exception on the second write. That's what Hibernate supports
beautifully.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
