i just looked at bob preston's patch which adds some text file support to hsqldb.
i'm wondering how hard it would be to add support for this in the jdbc connect string?
that way (at least in the case that i'd like all my tables to be text files), i needn't
make all my DDL be special cased, just b
i note that hsqldb is currently not using Thread.setDaemon(true) on its threads.
That means that they behave like user threads, and will prevent a program from
exiting, even after the main thread completes.
-mda
___
hsqldb-developers mailing list
[EM
I should add: ... if any hsqldb connections are left open at completion of main().
If you close all your connections, then the program exits when main() completes.
But note that this means that an uncaught exception may not exit your program,
if it throws past connection closing.
(this is all wi
the html files in demo/ just can't possibly work, unless i'm missing something.
for example, demo/memoryquery.html has:
-mda
___
hsqldb-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hsqldb-developers
> There is no link between WebServerConnection.java and the codebase="../lib/"
> in the demo html file. None whatsoever.
>
> I wrote the .html tags when I did the packaging for 1.60 and tested
> QueryTool successfully as an applet.
i'm guessing you aren't using hsqldb's mini web server then?
my
> If you are using the WebServer, you can put a copy of the hsqldb.jar
> ...
right; i know how to make it work (otherwise this would be on the users
discussion list :)).
my point is that either it should be made to work with the WebServer
(unlikely, since that would undermine file: url browsing),
The reason that in many databases a client prepare() call does not talk to the
server, is that the server implements a parse cache which largely obviates it.
In oracle they call this the "shared sql cache".
This makes sense actually -- since it is primarily server work that is being saved,
that
