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 05:07:32 GMT
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

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