of persistence capable objects they still will be passed to the cache on
commit).
regards,
Armin
-steve
Steve Clark
ECOS Development Group
[EMAIL PROTECTED]
(970)226-9291
Armin Waibel <[EMAIL PROTECTED]>
11/19/2005 08:13 PM
Please respond to
"OJB Users List"
To
y to mark a table as
completely off-limits for update?
-steve
Steve Clark
ECOS Development Group
[EMAIL PROTECTED]
(970)226-9291
Armin Waibel <[EMAIL PROTECTED]>
11/19/2005 08:13 PM
Please respond to
"OJB Users List"
To
OJB Users List
cc
Subject
Re: Old bug returns: UPDATE when
Hi Steve,
[EMAIL PROTECTED] wrote:
I am seeing what looks like an old OJB bug resurfacing, and wonder if
anybody can shed some light.
I have an object with a reference to a read-only lookup table, and also a
collection of entries from another read-only lookup table. Both lookups
have accept
I am seeing what looks like an old OJB bug resurfacing, and wonder if
anybody can shed some light.
I have an object with a reference to a read-only lookup table, and also a
collection of entries from another read-only lookup table. Both lookups
have accept-locks="false":
