You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/10/17 07:14:44 UTC
[jira] Created: (GERONIMO-1081) CMP create causes update SQL too
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.0
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
[jira] Updated: (GERONIMO-1081) CMP create causes update SQL too
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1081?page=all ]
Aaron Mulder updated GERONIMO-1081:
-----------------------------------
Assign To: Gianny Damour
Not sure if this is still the case, but please evaluate this issue when you get a chance (not necessarily for 1.1)
> CMP create causes update SQL too
> --------------------------------
>
> Key: GERONIMO-1081
> URL: http://issues.apache.org/jira/browse/GERONIMO-1081
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: OpenEJB
> Versions: 1.0-M5
> Reporter: Aaron Mulder
> Assignee: Gianny Damour
> Fix For: 1.2
>
> 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
[jira] Updated: (GERONIMO-1081) CMP create causes update SQL too
Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1081?page=all ]
Matt Hogstrom updated GERONIMO-1081:
------------------------------------
Fix Version/s: 1.x
(was: 1.2)
> CMP create causes update SQL too
> --------------------------------
>
> Key: GERONIMO-1081
> URL: http://issues.apache.org/jira/browse/GERONIMO-1081
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: OpenEJB
> Affects Versions: 1.0-M5
> Reporter: Aaron Mulder
> Assigned To: Gianny Damour
> Fix For: 1.x
>
>
> 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
[jira] Closed: (GERONIMO-1081) CMP create causes update SQL too
Posted by "Gianny Damour (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gianny Damour closed GERONIMO-1081.
-----------------------------------
Resolution: Won't Fix
Superseded
> CMP create causes update SQL too
> --------------------------------
>
> Key: GERONIMO-1081
> URL: https://issues.apache.org/jira/browse/GERONIMO-1081
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: OpenEJB
> Affects Versions: 1.0-M5
> Reporter: Aaron Mulder
> Assignee: Gianny Damour
> Fix For: 1.x
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-1081) CMP create causes update SQL too
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ 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