Yikes!! Could it be that simple!? Stay away from getResource() and just use that URL? I'll give it a try.
BTW, we did find that having the DB compressed in our JAR file increased the query time substantially. So in our JAR file we specified no compression. But we are wondering what will happen if the creator of the parent JAR chooses compression -- will our JAR (and DB) also be compressed? BTW, my partner did find a creative workaround. When our JAR launches, he executes a singleton which simply copies the DB file to the /tmp directory (Linux) and then we simply access the DB as a remote file (outside the JAR). Maybe that will help someone else traveling down this road. Many thanks Noel!! On Thursday, November 9, 2017 at 10:43:36 PM UTC-8, Noel Grandin wrote: > > http://h2database.com/html/features.html#database_in_zip > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
