geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gianny Damour <>
Subject Re: Geronimo CMP update statements
Date Thu, 26 Jan 2006 12:15:34 GMT
Hi Dan,

At the beginning, I was not seeing this as an issue. Based on your 
remark that triggers are wrongly fired, I now see this as an issue that 
needs to be fixed.

Could you please raise a JIRA for this problem?


Daniel John Debrunner wrote:

>At ApacheConUS 2005 I talked with Matt Hogstrom about the SQL UPDATE
>statements Geronimo was issuing against Derby for DayTrader.
>A single UPDATE statement is generated for a table that updates all
>columns using a CASE statement to ensure un-modified columns are not
>changed, or in reality changed to the same value. An example is
>described in GERONIMO-1080, the syntax may be a little different for Derby.
>I see two issues with this approach, one is that for Derby this is
>inefficient, and two, and probably more important, all SQL update
>triggers will fire due to this modification of all columns. Thus if an
>application defines a trigger on update of the address column of a
>customer table, then when using Geronimo this trigger will fire, even if
>the CMP application is only updating the customer's balance. This just
>seems the wrong semantics to me.
>Matt had said this was a known issue, and that it was going to be fixed.
>The comments in GERONIMO-1080 seem to indicate that this may not be seen
>as an issue, though those comments are dated before ApacheCon.
>I searched Jira and couldn't see any bug for changing this, are there
>any plans to address this?

View raw message