your best option is probably to keep the objects in a session that's
specifically for the global objects. Most important is that if you
are using multiple threads, you never call flush() on this session.
With regards to threadsafety in this case, as long as the session is
not used for a flush()
On Sat, 28 Jul 2007 14:36:45 -
Michael Bayer [EMAIL PROTECTED] wrote:
your best option is probably to keep the objects in a session that's
specifically for the global objects. Most important is that if you
are using multiple threads, you never call flush() on this session.
With
On Jul 28, 5:36 pm, Michael Bayer [EMAIL PROTECTED] wrote:
your best option is probably to keep the objects in a session that's
specifically for the global objects. Most important is that if you
are using multiple threads, you never call flush() on this session.
With regards to threadsafety
On Jul 28, 11:08 pm, Michael Bayer [EMAIL PROTECTED] wrote:
theres nothing at all wrong with the above; the only adjustments Id
make are to a. leave a global session open for your directory.root,
and b. remove all cascade rules from the parent relation (in this
case using
On Jul 28, 2007, at 8:46 PM, MuTPu4 wrote:
On Jul 28, 11:08 pm, Michael Bayer [EMAIL PROTECTED] wrote:
theres nothing at all wrong with the above; the only adjustments Id
make are to a. leave a global session open for your directory.root,
and b. remove all cascade rules from the parent
