@michael: changed to after_commit
@ivan:
Sorry for the late reply. Here's a decent example. I have this
working in production error free, but it's hardly done. Note, the
code below is a specific example. Let me know if you have questions
from sqlalchemy import orm
def get_session_id(session)
Hi Zende,
I am very curius about your caching layer. We are currently trying to
do the same using serialization from sqlalchemy.ext. What did you use?
Could you send me some examples?
Cheers,
Ivan
On Dec 14, 8:47 pm, zende wrote:
> I wrote a simple layer on top of my models that allows them to
zende wrote:
> I used SesionExtension.after_flush. Worked great.
>
> Thanks for the help Michael!
if you are using transactions with isolation, the changes within the
transaction wouldn't be visible to other connections until commit, which
implies after_commit() might be the better target - thoug
I used SesionExtension.after_flush. Worked great.
Thanks for the help Michael!
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to
sqlal
