You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by Apache Wiki <wi...@apache.org> on 2006/09/23 00:01:06 UTC
[Db-derby Wiki] Trivial Update of "JavaTableFunctions" by DanDebrunner
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.
The following page has been changed by DanDebrunner:
http://wiki.apache.org/db-derby/JavaTableFunctions
------------------------------------------------------------------------------
General.
- * Maintaining the table's state from a Java '''static''' method seems hard. The StringBuffer (or the alternative of a String object) is where the state is meant to be stored. Saving object state to and from a StringBuffer on every call seems very expensive. Maybe some scheme of a unique tag saved using the StringBuffer, and then a static HashMap in the class of the method to map the tag into the state. How to generate uniqueness and how to ensure cleanup?
+ * Maintaining the table's state from a Java '''static''' method seems hard. The !StringBuffer (or the alternative of a String object) is where the state is meant to be stored. Saving object state to and from a StringBuffer on every call seems very expensive. Maybe some scheme of a unique tag saved using the !StringBuffer, and then a static !HashMap in the class of the method to map the tag into the state. How to generate uniqueness and how to ensure cleanup?
As a VTI replacement