Hi Ray, > I have been using HSQLDB 1.8.0.5 in native mode, > as noted in my previous messages. > OO Base 2.0.3 only mentions HSQL 1.8.0 in database/property. > The x in OO Base HSQL 1.8.0.x is unknown. > 1.7.0.x is the major change version as noted in your message. > 1.8.0.5 is newer and should work for all connections > to both external (native, outside of *.odb) and > embedded (*.odb/database/script) HSQL DB. > Is it correct?
Not completely. 1.7.2 was the version where we introduced the "embedding"-capabilities in HSQLDB. > Can you please explain again on why > only connections to embedded HSQL > (*.odb/database/script) are affected, > not connections to external HSQL > (*.script, outside of *.odb), > if the above analysis is valid? When we initialize a connection, we tell HSQL to *not* access/store its files in the file system, but via some (OOo-implemnted) wrapper which re-routes those file accesses to the .odb file. Versions prior to 1.7.2 to not recognize the additional parameters we use for this purpose, they simply ignore them. So, those versions - and I suppose the one shipped with your banking application - continue to do file system access, and then fail because the respective files do not exist in the file system, but only in the .odb. External HSQL connections are not affected since those are understood by both the old and the recent HSQLDB version. > Does HSQLDB 1.8.0.5 break something? > Does it occur only on my PC (MS Windows XP)? > Is this problem reproducible on other PC's > (other MS Windows XP, Apples, UNIX)? I have never seen it happening, but we have reports from various users which we think are related to the problem. IIRC, those were on both Windows and Linux. > qa.openoffice.org/issues/show_bug.cgi?id=69624 > multiple drivers in class loading path > (not necessarily same or compatible version) (hmm, I overlooked you already know this issue, so I would not have needed to point you to it in my previous mail.) > I suggest some enchancement to the request in issue 69624: > > * define an OO user option of configurable path list > to control the loading sequence of OO classes > > in analogy to Java CLASSPATH or MS Windows PATH > OO system option is preferrable (Tools - Options) > No need to deal with environment variable > (different for MS, Apple, Unix) That's more a OOo-wide option, which I would not want to do in the course of this particular issue, is it is of more general nature (and requires some more overhead which would delay 69624 :-\). (Feel free, however, to submit an issue for this.) I suppose this would be some kind of editing the pre-configured paths. Effectively (at least after 69624 is fixed), OOo would behave as if "<ooo_installation>/program/classes/hsqldb.jar" were added to Tools/Options/Java/Classpath, and as if this path would be the very first to consider. Your suggestion could then be implemented allowing to customize those "implicit" classpaths, i.e. making them explicit. > * always include version in driver file names, > like (usr lib dir)/java classes/hsqldb 1.8.0.5.jar, > for management of version conflict Well, by definition, the versions should stay compatible, so there should be no need for this. I would prefer a better error detection here: When HSQL doesn't recognize our embedding parameters, then this shouldn't be ignored silently. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
