On Oct 22, 2007, at 4:25 AM, alain D. wrote:
Obj is a simple python object with on field (key : String(10)) mapped
to a table with on field (key) with is the primary key.
Session is defined like this :
engine = create_engine(**mysql_string**, strategy='threadlocal',
pool_size=50)
I forgot to say that I use mysql with InnoDB backend
(autoflush=True,transactional=True)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
On Oct 22, 2007, at 1:43 PM, alain D. wrote:
thanks a lot for you reply ...
If I understand correctly, a simple sess.begin() in #2 executed
right after the #1 commit will work (?). But I tested it and I still
dont get the commited object ...
What am I missing
no, a sess.rollback() or
On Apr 2, 2007, at 10:35 PM, Barry Warsaw wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Our populate_instance() checks the isnew flag and if this is true, it
does not call our initialization stuff. Now, I don't really see the
isnew flag documented, so I assumed it was only called
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 3, 2007, at 9:35 AM, Michael Bayer wrote:
OK, yes, im sorry about the lack of docs for isnew...sometimes i
subconsciously want to see how long it takes for someone to ask me
about something (bad habit) although in this case that flag is
On Apr 2, 2007, at 1:46 PM, Barry Warsaw wrote:
The problem is that if we call session.expire(mlist) /after/ the
MailList.__lock attribute gets set, it appears as though SA 'messes'
with this attribute. I've proven that if the session.expire() gets
called after MailList.Lock(), during the
