Hi Ray,
> It is not a limitation. It is more about design choice. Losing
> "all-in-one-file" package convenience (for maintenance on user side),
> and losing OO Base GUI (for occasional manual admin.). There is not
> much value left to keep OO Base in the integration list. So OO Base
> is effe
Dear Frank:
Thanks for the suggestions.
> Marc's idea with a HSQLDB server, which can be connected from both
Base and other applications, sounds like a good idea to me. You loose
the all-in-one-file then, of course, not sure how much this is a
limitation in your scenario.
It is not a limitation
Am Donnerstag, den 21.06.2007, 22:20 +0200 schrieb Marc Santhoff:
> See the HSQLDB documentation.
I did and found another interesting topic:
brosing to:
http://hsqldb.org/web/hsqlDocsFrame.html
and selecting "Documentation index" i read:
(direct link: http://hsqldb.org/doc/guide/ch01.html#N101
Dear Marc:
Thanks for your time in the deliberation.
> Use HSQL in server mode (as opposite to OO.o-embedded mode) and let
OO.o and the custom java applications connect to them as needed.
Yes, this approach would work, as found in my previous trial. OO is
almost completely out of the picture, t
Am Donnerstag, den 21.06.2007, 21:25 +0200 schrieb Frank Schönheit - Sun
Microsystems Germany:
> Hi Marc,
>
> > - Could the internal HSQL data be dumped out (maybe in SQL like making a
> > complete dump of common sql server data) and pumped into a central
> > server?
>
> "SCRIPT 'path_to_file'" w
Hi Marc,
> - Could the internal HSQL data be dumped out (maybe in SQL like making a
> complete dump of common sql server data) and pumped into a central
> server?
"SCRIPT 'path_to_file'" will create a dump of the database, which can be
used to re-create the complete DB. See the HSQLDB documentati
Hi Frank, Ray,
Am Donnerstag, den 21.06.2007, 14:40 +0200 schrieb Frank Schönheit - Sun
Microsystems Germany:
> You loose the
> all-in-one-file then, of course, not sure how much this is a limitation
> in your scenario. Also, it still means you have two separate connections
> to the DB, while in y
Hello Ray,
> * wait for OO API to support Connection and XConnection conversion
>
> Waiting period is uncertain.
> Waiting time is not likely on my side.
I meawhile even think this might be impossible. If you connect to a
running OOo instance, which may run in another process, then you have
Am Mittwoch, den 20.06.2007, 23:59 +0200 schrieb Marc Santhoff:
> > Many applications are designed and based solely on the OO Base *.odb
> > files. The *.odb files are used either as the sole gateway to other
> > JDBC data sources (MySQL, Oracle, etc.) or as a genuine data source
> > (embedded HSQ
Am Mittwoch, den 20.06.2007, 17:07 -0400 schrieb Jahn, Ray (R.):
> Dear Marc:
Hi Ray,
> Thanks for suggestions.
>
> > E.g. why do you have to fetch the connection from OO.o, wouldn't
> simply using the same database URL do for the different parts of the
> application?
>
> > Maybe embedding OO.o
Dear Marc:
Thanks for suggestions.
> E.g. why do you have to fetch the connection from OO.o, wouldn't
simply using the same database URL do for the different parts of the
application?
> Maybe embedding OO.o via the OO.o-java-bean can help rearranging the
relations between application parts?
> w
Am Dienstag, den 19.06.2007, 10:33 -0400 schrieb Jahn, Ray (R.):
> alternative subjects: (none possible in 2.2.0)
> * universal SQL application code
> * conversion between java.sql.Connection
> and sdbc.XConnection
> * Base linked tables
>
> Dear Frank Schönheit (OO Base team):
I'm neither Fran
alternative subjects: (none possible in 2.2.0)
* universal SQL application code
* conversion between java.sql.Connection
and sdbc.XConnection
* Base linked tables
Dear Frank Schönheit (OO Base team):
This is a continuation of previous discussions in various OO forums [1, 2, 3].
Please redirec
13 matches
Mail list logo
