Hi, Frank:
Thanks for advice. I am also relieved
after the identification of the root cause.
Some questions follow.
Thanks.
Ray
-----
Ray Jahn wrote:
> There is one thing unclear to me.
> Apparently the same driver modules
> are invoked for all OO connections to HSQL,
> including external and embedded databases.
> Can you explain why only connections to
> embedded databases (*.odb/database/script)
> are affected?
Frank Schönheit wrote:
> In the course of the HSQL integration, we extended HSQL with
> functionality to work in embedded mode. This extensions became part of
> official HSQL releases, from (IIRC) 1.7.2 onwards. So, from this version
> on, HSQL can work embedded and "normal".
> Now when you have an HSQL version which does not yet have those
> extensions, then it will simply not understand the embedding requests it
> gets from OOo, and ignore them. It will always try to open a "normal"
> connection.
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?
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?
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)?
-----
qa.openoffice.org/issues/show_bug.cgi?id=69624
multiple drivers in class loading path
(not necessarily same or compatible version)
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)
* always include version in driver file names,
like (usr lib dir)/java classes/hsqldb 1.8.0.5.jar,
for management of version conflict
User configurable path list is more flexible and useful due to
the shared library nature of many component softwares.
Examples include HSQL DB, SQLite DB, BeanShell, Ruby, etc.
HSQL DB can be invoked by its own UI, by OO Basic,
by BeanShell, by Ruby, by IBM Eclipse, etc.
BeanShell can be invoked by its own UI, by OO API, etc.
In others words, they resemble shared libraries,
like MS *.dll and UNIX *.so libraries.
For shared libraries, it is much less headache to
maintain only one copy at one central location.
________________________________________
PeoplePC Online
A better way to Internet
http://www.peoplepc.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
