On 10 Kvě, 18:06, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> > 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? In conjuction with primary key 'per se' probably not. At least MySQL accepts such syntax in contraty to reference guide: [UNIQUE [KEY] | [PRIMARY] KEY]. The concern is Django-Evolution, because it seems that DB generated prior/post 1:1 refactoring is different, more http://groups.google.com/group/django-evolution/browse_frm/thread/324fc03826fa5064 Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
