db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@apache.org>
Subject Re: The perils of complexity - CURRENT TIME handling
Date Fri, 01 Sep 2006 20:09:03 GMT
Daniel John Debrunner wrote:

> Hence all this complexity lead to significantly increased memory usage
> in the ResultSet tree and saving of one field in the activation. Exactly
> the opposite effect that was intended!!

Turns out to be even worse. All the close cleanup method stuff has no
functional benefit. If a statement is using current time expressions
then its execute method always performs the reset (forget) of the time

The only value to the code would be to allow up to three objects to be
garbage collected sooner, either inbetween executions or between the
time of the last execution and the time the statement is closed. Simply
not worth it.


View raw message