Yip Ng wrote:
Another way is to specify which column in the trigger that will invoke
the trigger action.
Thanks Yip and Dan.I will hold off on the release note until we
have the fix and I understand the root cause and when the proper
checking is/is not done. For example I'd like to
Another way is to specify which column in the trigger that will invoke the trigger action. i.e.:CREATE TRIGGER update_test AFTER UPDATE OF INFO ON test REFERENCING OLD AS old FOR EACH ROW MODE DB2SQL
UPDATE test SET timestamp=current_timestamp WHERE testid=old.testid;On 8/7/06, Ka
Kathey Marsden wrote:
> Daniel John Debrunner wrote:
>
>> Then I think this would lead to a simpler action statement of
>>
>> UPDATE TEST SET TIMESTAMP = CURRENT_TIMESTAMP WHERE TESTID = OLD.TESTID
>>
>> A statement trigger might be best in this case, would result in a single
>> update statement
Daniel John Debrunner wrote:
Then I think this would lead to a simpler action statement of
UPDATE TEST SET TIMESTAMP = CURRENT_TIMESTAMP WHERE TESTID = OLD.TESTID
A statement trigger might be best in this case, would result in a single
update statement rather than N.
Hmmm
Well, this (
Kathey Marsden wrote:
> Kathey Marsden wrote:
>
>> Kathey Marsden wrote:
>>
>>> A few questions/concerns on this issue:
>>> 1) CORRECT TRIGGER DEFINITION:
>>
>>
>>
> I think this is it. To update the timestamp when info is updated we do
> this:
> 0 rows inserted/updated/deleted
> ij> CRE
Kathey Marsden wrote:
Kathey Marsden wrote:
A few questions/concerns on this issue:
1) CORRECT TRIGGER DEFINITION:
I think this is it. To update the timestamp when info is updated we do
this:
with 10.1.2.4
ij version 10.1
ij> connect 'jdbc:derby:wombat;create=true';
ij> CREATE TABLE
Kathey Marsden wrote:
A few questions/concerns on this issue:
1) CORRECT TRIGGER DEFINITION:
To get the semantics the user seems to want, which is to update the
timestamp when TESTID changes, is this how the trigger should be defined?
[snip wrong syntax]
Answer is no. Not sure why I
Rajesh Kartha (JIRA) wrote:
I also think the title of the issue also need to change to reflect that self
trigger does not throw ERROR 54038 in some cases.
A few questions/concerns on this issue:
1) CORRECT TRIGGER DEFINITION:
To get the semantics the user seems to want, which is to upda
[
http://issues.apache.org/jira/browse/DERBY-1603?page=comments#action_12426160 ]
Yip Ng commented on DERBY-1603:
---
Found the problem, will post the patch up for review after running some initial
tests.
> ERROR 54038: "Maximum depth of nested trig
[
http://issues.apache.org/jira/browse/DERBY-1603?page=comments#action_12426127 ]
Rajesh Kartha commented on DERBY-1603:
--
Yes, I agree this self trigger should have thrown the error everytime it was
executed and there should not be any spec
[
http://issues.apache.org/jira/browse/DERBY-1603?page=comments#action_12426099 ]
Yip Ng commented on DERBY-1603:
---
The problem is not the upgrade right? The update statement above throws
SQLSTATE 54038 as it self triggers to the max depth and thu
[
http://issues.apache.org/jira/browse/DERBY-1603?page=comments#action_12423970 ]
Rajesh Kartha commented on DERBY-1603:
--
I tried the scenario on a 10.2.0.4 alpha - (418118) database with 10.2.0.5
alpha - (424456) jars and the issue exist
12 matches
Mail list logo
