On May 27, 2008, at 7:15 PM, TP wrote:
We're using SA 0.4.4. We're creating non-threadlocal sessions that are
bound to an engine at session factory creation time. Any ideas for why
even after closing one session and creating a new session with the
session factory that we're seeing old
On May 27, 2008, at 5:35 PM, TP wrote:
From reading the docs, it sounds like calling .close() on a session
implicitly does a .rollback():
When the Session is closed, it remains attached, but clears all of
its contents and releases any ongoing transactional resources,
including rolling
We're using SA 0.4.4. We're creating non-threadlocal sessions that are
bound to an engine at session factory creation time. Any ideas for why
even after closing one session and creating a new session with the
session factory that we're seeing old data? If we do an explicit
commit or rollback,
