Hallöchen!
Russell Keith-Magee writes:
> [...]
>
> I might be missing something obvious here, but isn't this
> *exactly* what database transactions are designed to fix?
> Admittedly, you've got an unusual presentation born out of weird
> browser behavior, but making sure that two overlapping operations
> don't violate data integrity sounds like the textbook case for
> using transactions.
I agree that if the constraint can be expressed by an RDBMS
conditions, it should be expressed this way. However, this is not
always possible.
By the way, in our project, we considered database integrity errors
as internal errors that we never caught. Instead, we avoided them
by pre-checking the input data. Is this a bad approach?
Tschö,
Torsten.
--
Torsten Bronger Jabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
--
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
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
