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 > up with a duplication player record?
You will get a duplicated record. PK=None is Django's marker for creating a new row in the database. Obtaining a record, setting PK=None, then saving will keep the old record, and create a new record with the same field values (except for m2m fields, which will not be copied). 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 -~----------~----~----~----~------~----~------~--~---
