On 15/03/07, DuncanM <[EMAIL PROTECTED]> wrote: > > I have 2 classes:
This post is really too long to be able to understand what and where it's going on. "Revision matching query does not exist" is usually caused when you're trying to select something out of the database and your query coudn't match what you're looking for. DoesNotExist is an exception that notifies you of this and is something you should be catching, if you're doing selects that might not give you any results. Furtermore, this model looks a bit bloated. Maybe you should consider a M2M relation, with an additional field, that specifies the position of the player, instead of harcoding them as separate fields in your model. It's much more heavy and difficult to process in the way you've defined it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
