----- Original Message -----
From: "Jon Stevens" <[EMAIL PROTECTED]>
> Uh...Serge, eat your own dog food.
Well, although this argument is compelling, I'd still like to discuss the
idea a bit more. I'm wondering how much benefit does it give the lay user
over the basic file system storage. In theory it should provide more
reliability... if a file is getting saved when the JVM is forcibly stopped,
the file might get corrupted (or only 1 of the 2 files gets deleted), while
using a database (java or otherwise) would get around this. This is the
most compelling issue for me. I do have a concern about Java memory
usage... I think we'd have to run HSQL in a separate JVM to avoid
OutOfMemory errors when handling very large files. That creates process
management issues since that will be a second process started/stopped.
Loading a multimegabyte email message into memory is going to be cumbersome
as it is.
Looking through the docs, one of the current restrictions kind of jumped out
at me: "The size of Binary data is limited to about 32 KB (because UTF is
used) " Does this mean I can't have a LONGVARBINARY (or LONGVARCHAR) more
than 32k? If this is the case, we can pretty much stop considering it an
option, so I'm hoping it's not.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
