Date: Friday, January 13, 2006 @ 14:31:54
Author: marc
Path: /cvsroot/carob/carob/doc
Modified: memory (1.2 -> 1.3)
Added footnote about indirect deletes
--------+
memory | 19 ++++++++++++++++++-
1 files changed, 18 insertions(+), 1 deletion(-)
Index: carob/doc/memory
diff -u carob/doc/memory:1.2 carob/doc/memory:1.3
--- carob/doc/memory:1.2 Fri Jan 13 14:22:44 2006
+++ carob/doc/memory Fri Jan 13 14:31:54 2006
@@ -42,9 +42,26 @@
-------------------
So far, the only way allowed to free resources allowed is to delete
-the connection; this is too restrictive. So the .close() method
+the connection [1]; this is too restrictive. So the .close() method
provides partial clean-ups on any object. It *deletes* all lower
objects owned, frees any remote (database) resources held and frees
now obsolete local fields as a memory optimisation.
Some closed objects can be re-initialized and used again.
+
+
+
+
+Footnote
+--------
+
+[1] actually some actions may delete objects as a side-effect. For
+instance:
+- executing a new query with an existing Statement will delete all
+ ResultSets of the previous query ("copy-assignement" semantic);
+- Statement.getMoreResults(some_close_flag) may delete the previous
+ ResultSet of the current query.
+- others?
+
+But this is indirect; sometimes the user may want to "just free
+resources".
_______________________________________________
Carob-commits mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/carob-commits
