db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: Killing derby/tomcat
Date Thu, 09 Oct 2008 00:17:35 GMT
Walter Rogura <mist@sudus.eu> writes:
> Hi folks,
>
> I have a project running, where I use tomcat 6 and derby 10.4. Both work
> quite fine together. But I observed that after changing db entries via
> the web-interface and tomcat get accidentally killed not all changes
> have been considered.
>
> In my case I have a person A, B and C. B and C report to A, so they
> refer to A. Cascading considers that if A gets removed that the
> references of B and C should be removed and set to NULL.
> And indeed, after removing A and stopping tomcat, the references of B
> and C are set to NULL.
> But, when removing A waiting a few seconds and killing tomcat, B and C
> still refer to A.

Are you able to see how this integrity constraint is mapped to Derby
schema? Does the mapping use a REFERENCES .. ON DELETE CASCADE clause?

Dag

Mime
View raw message