Has anybody experience with running an embedded (in-process) HSQLDB where the database files are stored on a network drive?
I appreciate that performance may suffer, but this will be a fairly small database, so I can live with that. My concern is that reliability should not be affected (the Derby documentation, for example, specifically warns against network drive storage).
This may seem like an odd requirement, but there's method in it. I need to give clients a small application that they can run off a CD on any workstation, but which keeps its data on a corporate file server so that it's properly backed-up. I don't want to install a network database server because that will have to be agreed with the corporate IT infrastructure overlords, and I'd like my application to be in use before 2020.
Chris
