Thomas Hallgren <thhal@mailblocks.com> writes:
> This is all about access to the java class images, i.e. the actual byte
> codes that make out the Java functions that will execute. Class files
> are normally grouped into archives called jar files (zip format
> essentially) and the SQL 2003 standard for server side Java defines
> stored procedures for loading, replacing, and removing such jars. I've
> implemented them as functions. A loaded jar is unpacked and stored as
> individual class files in a table.
AFAICS you are choosing to do things in the hardest possible way, on
the basis of completely unfounded suppositions about performance gains.
I recommend the KISS principle. Leave the jar files as jars and let the
Java runtime system manage them.
regards, tom lane