GeoServer : Hsql Bindings
This page last changed on May 12, 2007 by cholmes.
This page describes the Spatial DB in a Box bindings for the Hsql database. Hsql is a popular java-based database (previously called Hypersonic SQL) often used as an imbedded database in Java applications.
a) The source code is attached to this page. (hsql_bindings.zip)
See the hsql documentation for how to setup a server. The unix quickstart (in the hsql manaul) is a simple place to start.
Start your server with a classpath that includes JTS and StaticGeometry:
java -classpath hsqldb.jar;jts-1.5.jar;spatialdb.jar org.hsqldb.Server
Connect to it normally:
java -jar lib\hsqldb.jar localhost-sa
Add the spatial functions aliases by executing the generated .sql file
Remember to use the "GeomFromWKT()" and "ToText()" functions!
1. The serialized form of the Geometries is the normal JTS serialized form (which may not be efficient space-wise or parse-time-wise). We should change this so its WKB based.
2. Hsql developers are currently working on GiST indexes, which means an Rtree spatial index can be implemented. I do not know the time frame for this.
3. See the Hsql Home Page for more information on what the database supports and some of its design tradeoffs.
4. Hsql is very easy to bind to - you can just call the functions directly from the database w/o doing any work. The generated .sql file is just convenience functions so you don't have to type "org.openplans.spatialDBbox.StaticGeometry." all the time.
5. use type "OBJECT" to store your geometries in a table.
|Document generated by Confluence on May 14, 2014 23:00|