-- How modular is the current transaction support integrated with the rest of HSQLDB?
Hard to say how modular it is, but it is a simple scheme and is covered in a few classes. Session keeps a list of rows deleted / inserted in memory and when a commit is performed, the list is discarded. If a rollback is performed, the inverse action is performed on the database and the list is then discarded. This simple scheme means changes by other sessions are visible (READ_UNCOMMITTED) and conflicts between actions by two sessions are not resolved. -- Who decides about possibel extensions of the SQL language support in HSQLDB? I am the maintainer and decide on these issues. My approach is to allow any useful extensions if they are modular (optional) and do not increase the core size and complexity. Extensions that are part of the SQL language _can_ increase core size and complexity to some extent. -- Is there a way, if and how two (or more) HSQLDB server instances can communicate together, if possible without using SQL angain?! Yes, support for this has been developed as proof of concept (HSQLDB/R by Bela Ban - downloadable from our files section) using JGroups. We would like to make this a standard extension when we have improved the core for wider transaction isolation support. We would like to move to multi-version concurrency control in the core (it is possible to do this without radical changes). I don't know what "cache-constrained based caching enhancements" is, but any enhancement sounds like a good idea :) Your work could fit neatly with our future plans so I would welcome your involvement. Fred Toussi ----- Original Message ----- From: "Daniel Schaller" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: 18 January 2004 15:29 Subject: [Hsqldb-developers] Better Transaction Handling and Cache Enhancement Hi, I and a fellow student of me are currently working on our diploma thesis at the Dresden University of Technology (Germany), Chair for Database Technology. Our thesises deal about multi-version concurrency control and cache-constrained based caching enhancements in relational databases. To implement our features we have decided to use HSQLDB because it is written in Java and the source code is free available. Furthermore, we have to implement our features as a kind of core extension of relational database and not just as a middleware approach. We would like to know if you as the HSQLDB developers are interested in these features. If you should be, it would be nice, if you could give us some hints about the following questions: - How modular is the current transaction support integrated with the rest of HSQLDB? - Who decides about possibel extensions of the SQL language support in HSQLDB? - Is there a way, if and how two (or more) HSQLDB server instances can communicate together, if possible without using SQL angain?! Thanks in advance Daniel ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ hsqldb-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
