Am 18.03.2012 08:56, Mark Stanton wrote:
I think the point Mark was making was to switch away from using the
embedded back-end to pretty much any external one. Which is what
you often suggest too.
Yes indeed.
Can HSQLDB be used as an external engine? I thought not, which is why I didn't
include it.
Mark Stanton
One small step for mankind...
http://hsqldb.org
Download the latest version.
Put it somewhere in your libraries (no installation required).
Point your office Java to the extracted hsqldb.jar.
Extract ./database/ from your embedded database somewhere to your files.
Rename your database files with a common "dbname." prefix.
Connect a new Base document using JDBC with an URL like this one (refer
to the downloaded documentation in your libs):
jdbc:
hsqldb:file:/home/andreas/hsqldb-2.2.5/databases/Praxis/hsqldbdata/db0/chargen;default_schema=true;shutdown=true;hsqldb.default_table_type=cached;get_column_name=false
Copy over the queries, forms and reports from your embedded thing.
You get the latest version of a full featured HSQLDB without
restrictions, many more functions, the access control and safety you
would expect from a database application.
You can write a configuration file to run a server for concurrent access.
Drawbacks:
- Embedded HSQL requires another Java config. I use OOo for embedded and
LibO 3.3.4 for "normal" access.
- Base can not handle user defined row filters with HSQLDB2. I use my
own "power filters" anyway.
--
For unsubscribe instructions e-mail to: [email protected]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
