On 7/12/06, Jay Parlar <[EMAIL PROTECTED]> wrote: > Is there a better way to do this? More specifically, an atomic way to > generate and set the new unique_id? I can't just use the autogenerated > 'id' primary key as an unique identifier, because I have a list of > legacy unique_id values which I have to initially populate the db > with.
Use the auto-incrementing "id" field. Populating the DB with some explicit values shouldn't pose any problems in that case. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
