PS: I should also mention the currently accepted work around, which is
to force the tables creation order by declaring in your model:
soClasses = ('Address', 'AddressArea', 'AddressCity')
Quick and easy enough if your model has only a few entities. Note that
it is an imperfect workaround: the "sql create" will work, but the "sql
drop" will most likely fail. (See bug #882 for more about this).
Anyway, I don't know if anybody else but me gave the patch in #279 a
try, so if you do try it, please let us know if it worked for you.
Cheers,
--
Yves-Eric
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---
