Got'cha! That worked ... I'm now converted over to 0.95!
Thanks for all of your great help Russ!
-Sandy
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to dj
On 11/2/06, ZebZiggle <[EMAIL PROTECTED]> wrote:
>
> Wow ... I had no idea about that. I must have a ton of duplicate
> records in production now. (more homework).
>
> What's the correct way to set a related object to null?
By assignment, just as you would with any other attribute (i.e.,
instance
Wow ... I had no idea about that. I must have a ton of duplicate
records in production now. (more homework).
What's the correct way to set a related object to null?
-S
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Group
On 11/2/06, ZebZiggle <[EMAIL PROTECTED]> wrote:
>
> Thx Russ!
>
> >> player.user.id = None
> >> player.save()
>
> >Yes. (assuming that the desired behaviour is to create a new
> > player as a result of your save)
>
> I assume you mean that player will get a new ID, but not that I'll end
>
Thx Russ!
>> player.user.id = None
>> player.save()
>Yes. (assuming that the desired behaviour is to create a new
> player as a result of your save)
I assume you mean that player will get a new ID, but not that I'll end
up with a duplication player record?
--~--~-~--~~
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, a
What is the format for __id in filters?
Does this code look correct (assuming characterDefinition is a member
of GameElement):
game.gameelement_set.filter(characterDefinition__id = characterId)
Note the two underscores. Also, I'm assuming gameElement_set gets
changed to lower-case "gameelement
7 matches
Mail list logo
