On Mon, 2006-10-09 at 05:31 -0700, Panos Laganakos wrote: > > There are a few corner cases for objects that only have an implicit > > primary key field like this. Working with them in the admin interface is > > one of the areas that may or may not work. It's not really worth us > > putting in an enormous amount of time to get all of this ironed out, > > since you can trivially get the same effect using an explicit primary > > key (just define the primary_key attribute on a field) and then > > everything should work smoothly. Or you can just fold the empty model > > into one of the classes it's used in and get rid of it altogether, since > > it's isomorphic to having an integer field where the ForeignKey > > currently is. > > Unfortunately, specifying an explicit primary key in the form of: > > class Dvd(models.Model): > id = models.AutoField(primary_key=True) > > Didn't work, and I still get an "... out of range" error when I try to > add one. Only way I could bypass this error is adding a dummy 'name' > CharField which doesn't get used. I'd like to avoid doing so though. > > Any ideas?
May well be a bug. It would be useful if you could work out exactly what is happening (what list it is trying to access that is empty, for example) and file a ticket with the details. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---