Yuen Ho Wong wrote: > I was just wondering if the db sessions TG 1.0.4 HEAD creates uses > transaction. I was reading the turbogears.database module and I > noticed that TG uses the non-transactional create_session() instead of > the recommended sessionmaker() function, which can be set to use > transactions.
If we would change the session to be transactional, this would break the identity provider and maybe other things, since TG silently assumes that we are working with non-transactional, non-autoflush sessions. However, it may be a good idea (for TG 1.1) to add configuration options such as sqlalchemy.transactional and sqlalchemy.autoflush that are evaluated by TurboGears to setup sessions and deal with them afterwards. -- Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
