It appears I have answered my own question. If I explicitly compile
the mapper of the object that is in the beaker session on the model
initialization then it resolves the problem. The only problem left is
explaining why this is so?
What strangeness is the beaker session up to that it gets arou
Hi,
Disclaimer: I have kinda cross posted this over at the SQLAlchemy
mailing list in an effort to trace down the corner of pylons that may
be responsible for the following behaviour:
I have a pylons application using file based beaker sessions. I
retrieve a mapped object from the database, det
