}
With the above style of coding our models, we don't get
ConcurrentModificationException, but any update statement to the
parent_table does not use version column.
Please throw some light on these behaviors.
Regards,
Naresh
P.S. The model and sample client code follows.
--
class
is correct.
Regards,
Naresh
On Mon, Nov 29, 2010 at 2:21 PM, Naresh nkhal...@vayana.in wrote:
Hi,
We have a parent class/table (Notification/notifications) and a child
class/table(BusinessNotification/business_notifications).
Both of them have a version_id_col defined.
We are facing
Thanks Michael for the confirmation/explanation.
On Nov 29, 8:25 pm, Michael Bayer mike...@zzzcomputing.com wrote:
On Nov 29, 2010, at 8:28 AM, Naresh Khalasi wrote:
Hi,
After some more internal discussions we tried and realized that the version
col is not really required at the child
Thanks Mike for all the explanations.
On Mon, Sep 28, 2009 at 7:54 AM, Michael Bayer mike...@zzzcomputing.com wrote:
nkhalasi wrote:
However with this I am getting unwanted commits. Essentially when the
newid(ctx) function executes the update it also does an commit which
results into my
