Topic
1 reply Latest Post - ‏2007-03-19T23:17:53Z by Stan
dportabella
dportabella
1 Post
ACCEPTED ANSWER

Pinned topic Derby, Applets and temporary files

‏2007-03-19T22:22:16Z |
According to the documentation, with Derby we can deploy applets with read-only databases packed as a jar file.

However, Derby creates temporary files for complex queries, such as SELECT DISTINCT:
https://issues.apache.org/jira/browse/DERBY-2354
http://db.apache.org/derby/docs/10.2/tuning/rtunproper34037.html

Is it possible to use a derby database (packed in a jar file) from an applet, without having Derby creating any temporary file?
(and so, no need to have signed applets. so, no need to ask the user to trust the applet)

Regards,
DAvid
Updated on 2007-03-19T23:17:53Z at 2007-03-19T23:17:53Z by Stan
  • Stan
    Stan
    267 Posts
    ACCEPTED ANSWER

    Re: Derby, Applets and temporary files

    ‏2007-03-19T23:17:53Z  in response to dportabella
    There is not a way to tell Derby not to use temporary files. You can set the location of the files setting derby.storage.tempDirectory but this will still require write permissions for the applet. Have you considered handling your persistant storage needs by using servlets? This will avoid the many restrictions placed on applet processing.