On 24/05/2020 19:34, Bryan Pendleton wrote:
Interesting. Can you let the Squirrel community know about this?
I wonder if this is related to the switch from Java 8 to Java 9 across
the Derby 10.14 to 10.15 boundary?
Can you tell what version Squirrel was pre-packaging, and what version
you used instead?
thanks,
bryan
Looking at the Squirrel version, the file called derby.jar contains the
following directory structure (using du):
3 net/sourceforge/squirrel_sql/plugins/derby/exp
7 net/sourceforge/squirrel_sql/plugins/derby/prefs
14 net/sourceforge/squirrel_sql/plugins/derby/tab
4 net/sourceforge/squirrel_sql/plugins/derby/tokenizer
20 net/sourceforge/squirrel_sql/plugins/derby/types
65 net/sourceforge/squirrel_sql/plugins/derby
65 net/sourceforge/squirrel_sql/plugins
65 net/sourceforge/squirrel_sql
65 net/sourceforge
65 net
So no wonder it didn't work. I naively assumed that a file called
derby.jar would be an actual Derby distro. (Incidentally, the manifest
says it was built with JDK 1.8.0_192.)
My derby.log says "10.9.1.0 - (1344872)" -- I haven't upgraded for ages,
and am still on Java 1.8 myself. It ain't broke so I'm not fixing it.
--
John English
