I managed to pull off a backport of the HSQLDB 2 data to HSQLDB 1 with the
encoding surviving. The process was painful. Meanwhile, we managed to get
the legacy system upgraded to have hsqldb 2, so life is much better.
In the process, I did notice a strange thing. The hsqldb 2.4.1 upgrade
commit claims to change the catalog version, but has no change to EPSG.zip.
- public static final Version VERSION = new Version("8.6.0.0");
+ public static final Version VERSION = new Version("8.6.0.1");
Looking in the head of master I see that it has indeed not been updated -
8.6.0.0 done in 2015
unzip -p
modules/plugin/epsg-hsql/src/main/resources/org/geotools/referencing/factory/epsg/hsql/EPSG.zip
EPSG.properties
#EPSG database on HSQL
#Sat Jan 10 06:45:27 MST 2015
version=2.2.8
readonly=true
epsg.version=8.6.0.0
modified=no
https://github.com/geotools/geotools/commit/046c0c102470f6bea8162649eb1d44a9d63324d8
On Thu, Jan 17, 2019 at 4:10 PM Kurt Schwehr <[email protected]> wrote:
> Hi all,
>
> I've got a funky problem I am hoping one of you all can help me with...
> I am working on a legacy system that is stuck with HSQLDB 1 at the moment
> and trying to get it to use geotools 19 with the newer epsg_hsql CRS
> database. Using SCRIPT to dump the contents, hacking the results a bit,
> and then loading it into HSQL 1 looses proper encoding of things like the
> degree symbol. Any idea how to back port the contents of the the database
> to HSQL 1 correctly?
>
>
> https://stackoverflow.com/questions/54208286/exporting-hsqldb-database-with-utf-8-encoding
>
> Many thanks!
> -kurt
>
--
--
http://schwehr.org
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
