On 11/1/06, ZebZiggle <[EMAIL PROTECTED]> wrote: > > Does this code look correct (assuming characterDefinition is a member > of GameElement): > > game.gameelement_set.filter(characterDefinition__id = characterId)
Yes, it is correct. It follows the characterDefinition relation to another object, and looks for the ID member on that related object to check that it is equal to the provide characterID. In practice, the table join will be omitted because it is redundant. The following queries would be valid equivalents to your query: game.gameelement_set.filter(characterDefinition__pk = characterId) # pk -> __id__exact game.gameelement_set.filter(characterDefinition = characterId) # implies __id__exact game.gameelement_set.filter(characterDefinition = character) # Object, not ID > Note the two underscores. Also, I'm assuming gameElement_set gets > changed to lower-case "gameelement_set"? Yes. The related manager name is object_name.lower() + '_set' (unless overridden by related_name). > Finally, can I safely do this the same as before? > > player.user.id = None > player.save() Yes. (assuming that the desired behaviour is to create a new player as a result of your save) Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
