db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gabriele Kahlout <gabri...@mysimpatico.com>
Subject Re: how to cascade on update? Not possible?
Date Tue, 16 Mar 2010 07:26:29 GMT
Okay, and how do you recommend I work around it?
I should retrieve the effected tuples (the referencing) and store
their values (onto the stack/heap) and then delete the records (since
the referencing fields are primary keys), and then finally updated the
referred to tuples, and then re-insert the data into the referencing
table, with the appropriate modification.
Unfortunately violation checking is done after each statement, and may
not be deffered.

Would this be permissible?

 final Connection con = getConnection(false);
			final Statement st = con.createStatement();
                        final ResultSet rs =
st.executeQuery(SqlWrapper.select(objColumn, refTable, wColumn,

                        final Statement st1 = con.createStatement();
wColumn, currentSpelling));
			st1.executeUpdate(SqlWrapper.update(expTable, expColumn,
newSpelling, currentSpelling));

                        while (rs.next()){
                            rs.updateString(SqlWrapper.index, newSpelling);


2010/3/16, Sylvain Leroux <sylvain@chicoree.fr>:
> Hi,
> Just passing by:
> http://issues.apache.org/jira/browse/DERBY-735
> Regards,
> - Sylvain
> Gabriele Kahlout a écrit :
>> ya. Also SQLite does.
>> I tried to look where to submit feature requests (not bug reports),
>> but failed. Any links?
>> 2010/3/16, Rick Genter <rgenter@silverlink.com>:
>>> On 3/15/10 6:46 PM, "Ronald Rudy" <ronchalant@gmail.com> wrote:
>>>> I believe you want to look at this:
>>>> http://db.apache.org/derby/manuals/reference/sqlj32.html
>>>>  <http://db.apache.org/derby/manuals/reference/sqlj32.html> Specifically
>>>> the
>>>> referential ON UPDATE in constraints.  The only "ON UPDATE" actions that
>>>> are
>>>> allowed are "NO ACTION" and "RESTRICT"; Derby does not appear to support
>>>> cascading updates.  You can log a feature request, I believe there might
>>>> already be one for it based on this thread:
>>>> http://old.nabble.com/ON-UPDATE-CASCADE-in-derby-td1633870.html
>>>> Incidentally I do believe that MySQL supports on update cascade with its
>>>> INNODB engine, and I do think MS SQL does as well
>>>> (http://msdn.microsoft.com/en-us/library/aa275462(SQL.80).aspx)
>>> Thank you for the pointer. I learn something new every day ;-).
>>> --
>>> Rick Genter
>>> Principal Software Engineer
>>> Silverlink Communications
>>> rgenter@silverlink.com
>>> www.silverlink.com
>>> Office (781) 583-7145
>>> Mobile (408) 398-7006
>>> This e-mail, including attachments, may include confidential and/or
>>> proprietary information, and may only be used by the person or entity to
>>> which it is addressed. If the reader of this e-mail is not the intended
>>> recipient or his or her authorized agent, the reader is hereby notified
>>> that any dissemination, distribution or copying of this e-mail is
>>> prohibited. If you have received this e-mail in error, please notify the
>>> sender by replying to this message and delete this e-mail immediately
> --
> sylvain@chicoree.fr
> http://www.chicoree.fr

K. Gabriele

--- unchanged since 25/1/10 ---
P.S. Unless a notification (LON), please reply either with an answer
OR with " ACK" appended to this subject within 48 hours. Otherwise, I
might resend.
In(LON, this) ∨ In(48h, TimeNow) ∨ ∃x. In(x, MyInbox) ∧ IsAnswerTo(x,
this) ∨ (In(subject(this), subject(x)) ∧ In(ACK, subject(x)) ∧
¬IsAnswerTo(x,this)) ⇒ ¬IResend(this).

Also note that correspondence may be received only from specified a
priori senders, or if the subject of this email ends with a code, eg.
-LICHT01X, then also from senders whose reply contains it.
∀x. In(x, MyInbox) ⇒ In(senderAddress(x), MySafeSenderList) ∨ (∃y.
In(y, subject(this) ) ∧ In(y,x) ∧ isCodeLike(y, -LICHT01X) ).

View raw message