[
https://issues.apache.org/jira/browse/DERBY-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567613#comment-14567613
]
Lukas Eder commented on DERBY-6813:
---
[~bryanpendleton]: Thanks for the hints. I'm just
Hi Bryan,
A possible solution that occurred to me was, if we can change the structure
of DataDictionaryImpl.getTriggerActionString()
such that the order of columns in trigger's REFERENCING clause is changed.
Instead of looking up at the columns in action node first, if we put the
columns in
Hi Bryan,
//Now that we know what columns we need for trigger columns
and
//trigger action columns, we can get rid of remaining -1 entries
//for the remaining columns from trigger table.
//eg
//CREATE TRIGGER tr1 AFTER UPDATE OF c12 ON table1
//REFERENCING OLD AS oldt NEW AS
I'm sorry, I clicked on send by mistake without completing the mail,
So a possible solution that I have thought of is that if the arrays
- triggerActionColsOnly
- triggerColsAndTriggerActionCols
are different then I will sort the triggerColsAndTriggerActionCols array
such that the
[
https://issues.apache.org/jira/browse/DERBY-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinav Gupta updated DERBY-6783:
-
Attachment: sortFunction.diff
WHEN clause in CREATE TRIGGER for UPDATE is not working for the
Hi Bryan,
I tried implementing the sort logic and I've attached a patch for it. I
think the bug still hasn't been solved, I'll try to understand where I'm
going wrong with this logic or if there is a mistake with the
implementation.
On Tue, Jun 2, 2015 at 1:21 AM, Abhinav Gupta
[
https://issues.apache.org/jira/browse/DERBY-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14568473#comment-14568473
]
Bryan Pendleton commented on DERBY-6807:
I changed line 96 of
