Thanks for the replies, both. > This idea has occurred to me before, and I can see how it could be > useful, but I got caught up on one significant detail: how do you > handle references? When you specify the PK, you provide an identifier > to use as a cross reference. If this identifier no longer exists, what > do you use as a reference in its place?
I hadn't thought that far ahead. You're right. I'll give it some thought. > You shouldn't even need to write a PK counter - just save the objects > without a primary key, and the database will allocate the next > available key. The issue is how to cross reference. Heh, whoops! It didn't occur to me to set the pk to None, I was just omitting 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 -~----------~----~----~----~------~----~------~--~---
