You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org> on 2005/12/10 01:25:09 UTC

[jira] Updated: (GERONIMO-1081) CMP create causes update SQL too

     [ http://issues.apache.org/jira/browse/GERONIMO-1081?page=all ]

Matt Hogstrom updated GERONIMO-1081:
------------------------------------

    Fix Version: 1.1
                     (was: 1.0)

Moving to 1.1

> CMP create causes update SQL too
> --------------------------------
>
>          Key: GERONIMO-1081
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1081
>      Project: Geronimo
>         Type: Bug
>   Components: OpenEJB
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>      Fix For: 1.1

>
> I have a situation where I call a session bean method that does nothing but look up an Entity home and call create on it.  This result in an UPDATE SQL being executed, not just an INSERT.  It seems to me that for performance reasons if nothing else, we should perform just one INSERT.  (How do I know?  Because I ran into GERONIMO-1080 when calling the session bean method, which caused the create to always roll back, so I couldn't actually create anything -- another good reason to fix this.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira