[sqlalchemy] Re: SAContext and transactions?

2007-06-29 Thread Mike Orr
On 6/29/07, voltron [EMAIL PROTECTED] wrote: I´m not sure if I should ask this here or the Pylons forum: Here, but I haven't introduced SAContext here yet. SAContext is a little top-level organizer for engines, metadatas, and a session context. It was written for Pylons due to the confusion

[sqlalchemy] Re: SAContext and transactions?

2007-06-29 Thread sdobrev
SAContext is a little top-level organizer for engines, metadatas, and a session context. It was written for Pylons due to the confusion people were having setting up their models, but the SAContext class itself can be used in any SQLAlchemy application.

[sqlalchemy] Re: SAContext and transactions?

2007-06-29 Thread Mike Orr
On 6/29/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: http://sluggo.scrapping.cc/python/sacontext/ hmm, why have i invented same thing 8 months ago... Anyway. for a reason or another u dont have any destroy operations there. It's only a container. Its main job is to preserve the right

[sqlalchemy] Re: SAContext and transactions?

2007-06-29 Thread sdobrev
it's all okay. i just thought that if it is a Context, u should have some destructors - as u call many constructors. otherwise it is not reentrant - or at least repeatable. But if the idea is that this context will always be one-and-only, lives forever, and all db-stuff will happen within

[sqlalchemy] Re: SAContext and transactions?

2007-06-29 Thread Mike Orr
On 6/29/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: it's all okay. i just thought that if it is a Context, u should have some destructors - as u call many constructors. otherwise it is not reentrant - or at least repeatable. I only call it context because Mike uses the word for session