On Sat, May 10, 2008 at 1:30 AM, Peter Melvyn <[EMAIL PROTECTED]> wrote:
> I notices that refactored OneToOneField creates artificial primary key > as UNIQUE, whereas all other primary keys generated by Django omits > such declaration, because it is inherent (at least on MySQL) > > Setting kwargs['unique'] = False in OneToOneField constructor > supresses this, but I don know if there are no other dependencies... > Is the UNIQUE causing a problem? Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
