Thanks Fred.
There is no major difference between HSQLDB's understanding of a transaction
and the general use of this. As you say a transaction is basically what
happens between two ROLLBACK/COMMIT commands. Obviously different
implementation will need different internal data structures and these should
be named appropriately.
Ok, will try to make the best of all and when I have hopefully implemented the first step, the FOCC, I will post, what I have done (renaming, new things and so on)
Re packaging, it might be a good idea to change things at some point in the
future, but any publicly visible change would have an effect on the programs
that use HSQLDB. For example, putting the JDBC classes in a different
package would mean changing the connection code. You are free to put your
additions in a new Java package.
Ok, that's right and always a big problem/issue when making a big changes in a widespread system ;-)
Have a nice day!
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
