On 1/23/07, kavikaBldr <[EMAIL PROTECTED]> wrote: > > Thanks. Explicitly committing fixed the issue. > Would you recommend sqlalchemy over sqlobject?
If you don't have to access legacy databases (with tables where the unique key is composed of 4 columns per example...) then I would not push you to sqlalchemy. The standard component that has been chosen for TurboGears 1.0 branch is SQLObject and will stay that during all the lifetime of the 1.0 branch. When starting a new web application project from scratch you generally design your own database schema. So the legacy database argument falls upon itself here. If sqlobject does what you need why should you bother to switch? Using sqlalchemy with the current TurboGears branch means you cannot use model designer not catwalk. This may not impact you but this is definitely a point to balance during the decision process if you are not the only one evaluating the technical solution. Regards, Florent. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
