Re: Digest for - 3 Messages in 1 Topic

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: Digest for - 3 Messages in 1 Topic

Justin, all,

(I'm cc:ing this message also over to the Hibernate Spatial mailing list)

I have managed to overcome Hibernate's schema generation problem by
specifying SQL type of my geometry column in Hibernate mapping file.
Looking at the example below, the one I used looks like:

<property name="spatialGeographicReferenceBox"
  <column name="spatialGeographicReferenceBox" sql-type="BLOB"/>

This made it possible to generate the schema and then use it when
creating the database; I tested both inserting and querying the
spatial column and it seems to be working. So until the issue of
generating the schema with GeoDBDialect in Hibernate Spatial is fixed,
this solution can be used instead when you want to automatically
generate the schema from Hibernate mapping files.

I hope that clears up some things. Big thanks for that extension to
H2/GeoDB, it should help in our testing procedure!


On Wed, Aug 25, 2010 at 8:22 AM, Coquelicot <[hidden email]> wrote:

> Hi Justin,
> my Hibernate mapping looks like that (sorry for not using the
> attachment but my working environment prevents uploads of them):
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD
> 3.0//EN" "">
> <hibernate-mapping>
>  <class table="NSIL_COVERAGE" name="package.NSIL_COVERAGE">
>    <id access="property" name="id">
>      <generator class="native"/>
>    </id>
>    <property name="spatialCountryCode"
> index="NSIL_COVERAGE_sp_d14e1605_idx" length="20"
> column="spatialCountryCode"/>
>    <property name="spatialGeographicReferenceBox"
> type="org.hibernatespatial.GeometryUserType"
> column="spatialGeographicReferenceBox"/>
>    <property name="temporalEnd" column="temporalEnd"/>
>    <property name="temporalStart" column="temporalStart"/>
>  </class>
> </hibernate-mapping>
> As for the actual database table, I am using Hibernates ExportSchema
> task which basically takes the mapping like above and generates the
> DDL SQL for me. This procedure fails however, with the same ecxeption
> ('No Dialect mapping for JDBC type: 2003'). Because SchemaExport is
> using Hibernate dialect to do all this, we come to the starting point
> of this whole thread - GeoDBDialect is not providing proper types.
> Looking at the sources for GeoDBDialect here : ,
> it looks that it is extending Hibernate's H2 dialect so we shouldn't
> get the complaints about the array type (2003) missing.
> Łukasz
>> Justin Deoliveira <[hidden email]> Aug 24 10:23AM -0600 ^
>> Hi Lukasz,
>> 2003 looks like it is an array type. What is the schema of the table you are
>> trying to map? Also how does your GeoDB dialect work? Does it extend the
>> regular H2 one?
>> -Justin
hibernatespatial-users mailing list
[hidden email]