[ http://issues.apache.org/jira/browse/DERBY-751?page=all ]
Mike Matrigali updated DERBY-751:
---------------------------------
Component: SQL
(was: Performance)
changing module as discussion from mamta on the list indicates fix is in this
area of the code. Performance seems like a better "issue type" than a
particular module.
> Temporary tables with on commit delete rows should be touched at commit time
> only if they were modified in the transaction
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-751
> URL: http://issues.apache.org/jira/browse/DERBY-751
> Project: Derby
> Type: Improvement
> Components: SQL
> Versions: 10.0.2.0
> Reporter: Mamta A. Satoor
>
> Derby drops and recreates the conglomerate for a global temporary table at
> the commit time if the table was defined as on commit delete rows and there
> are no held cursors open on that table. But if the table was never modified
> in a transaction, we should not drop and recreate it.
> In order to support the proper rollback behavior of the temporary tables,
> Derby has some code which checks how the temporary tables were modified in a
> transaction. Probably that code can be used at the commit time as well to
> improve the performance of temporary tables.
--
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
