On 3月24日, 下午3时53分, Russell Keith-Magee <[email protected]> wrote: > On Thu, Mar 24, 2011 at 3:15 PM, dy <[email protected]> wrote: > > Hi Jacob: > > > Yes, you understand right!Thank you for your reply. > > > As you said,is this a bug of django1.2.3? Or this feature can be used > > in django-1.2.3, but at a higher version is disabled. > > > Moreover, in the official documentation(on this page:http:// > > docs.djangoproject.com/en/1.3/topics/db/multi-db/), I did not see that > > django does not support the primary foreign keys across databases.As > > you know , sometimes the demand is very strange , so I wonder why I > > can use it on django-1.2.3 and not on django-1.2.5 or higher > > version .This made me very confused. > > It was a bug in Django 1.2.3 that it was allowed at all. The > documentation has always said that cross-database foreign keys aren't > allowed [1]. In the process of fixing a different bug (the fix was > included in 1.2.4), the validation rules for foreign keys were > modified; you are now hitting those validation rules. > > [1]http://docs.djangoproject.com/en/1.2/topics/db/multi-db/#limitations-... > > Yours, > Russ Magee %-)
Hi Russ Magee, Thank you very much. I want to know if I continue to use it like this what problems will happen.If you or someone else have this experience,can you tell me? Thanks again. Dy -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
