Thanks again dallas and kenneth,

Kenneth's comment about the clean process sent me back to the docs. I
was using form.cleaned_data to do my own integrity checking, but I
didn't realize what was truly available from the clean methods.

Handling the validation with custom form methods does seem like the
way to go. I appreciate the feedback.

Dan J.

On Apr 21, 12:57 am, dallas lynn <[EMAIL PROTECTED]> wrote:
> I believe this is a postgres thing -- the transaction failed but
> postgres didn't rollback, and the message_set.create tries to put a
> message in the database.  it's kind of ghetto, but you can also try
> manually rolling back postgres when you catch the exception but before
> you set the message.
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to