On Wednesday 28 June 2006 14:02, Jorge Godoy wrote: > "Diez B. Roggisch" <[EMAIL PROTECTED]> writes: > > - no soClasses is generated - making generation of the tables impossible > > when more complicated models are used. I assume reordering the classes in > > the designer will fix this - yet computers are inherently better in > > calculation partial orderings, maybe some automatism could be created? > > It would be better if SQLObject created tables in the order they were > defined in the file instead of ordering them alphabetically... This is a > bug in SQLObject and it bothers a lot of people.
I doubt that is doable - there is no way (except maybe from entering trace-mode and monitor the modules dictionary, so make that an "easy way" and "doable but difficult") to get the order of declarations. And it would still require the user to rearange things - not very convenient. However, as the designer has the capability to show the dependency graph, it shouldn't be too hard to compute the partial ordering on that and spit out the soClasses-property. Or even do that in sql-object and make it automatically. Alternativel, one could first create tables, and then put the constraints on them. Next thing: circular references and deferred triggers... :) regards, Diez --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
