Re: InternalError and transactions

On Sat, 2009-01-24 at 11:56 -0800, Rob Hudson wrote: [...] > Based on what you describe above, it sounds preferable to let Django > handle the unique_together on is_valid(), but I don't think I can do > that since I need to attach the user to the form later since I don't > know it until the

Re: InternalError and transactions

On Jan 24, 11:41 am, Karen Tracey wrote: > Just a note -- what you are describing is unique URLs per-user.  You > confused me a bit with how you phrased it as duplicate URLs are allowed by > what you have specified, so long as they are associated with different > users.

Re: InternalError and transactions

On Sat, Jan 24, 2009 at 12:52 PM, Rob Hudson wrote: > > I'm a bit at a loss as to where to go from here... > > I have simple Link and Category models. My Link model is essentially: > user_id, category (FK), name, URL. I have a Meta unique_together on > (user, url) so no

InternalError and transactions

I'm a bit at a loss as to where to go from here... I have simple Link and Category models. My Link model is essentially: user_id, category (FK), name, URL. I have a Meta unique_together on (user, url) so no duplicate URLs get entered. I'm testing this by trying to purposefully enter a