> And if you have another documenting tool that generate your Python code or > if you write it by hand you miss the solution and have to compute it > yourself. I find it much more productive to write the classes by hand, > since I can control everything I want and I don't need to be going from one > screen to the other defining properties. So, in my case, solving the > problem in SQL Object would automagically work -- as it would for you in > any other tool different than mine -- while doing it inside the Toolbox > would just solve the problem for toolbox users.
I agree that solving it in SQLObject would be the best solution. > > Next thing: circular references and deferred triggers... :) > > > :-) There are no ways to define triggers on the database with SQL Object, Ah, I meant constraints. At least on oracle these can be deferred, so that you can have circular references with foreign key constraints. But then - its not sooo important. 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 -~----------~----~----~----~------~----~------~--~---
