Re: [Geotools-gt2-users] Using the default values in a new row.

[rBartel <alb...@gm...>]

I have discovered the problem, I believe. I have a few tables, all with the
same schema, and three have the problem above. The only difference is that,
in Geoserver, the three that don't work think that the column that is of
type Geometry in postgis is of type Point, whereas the ones that work think
the Geometry column is of type Geometry. I could not tell this from pgAdmin,
because it displays them all the same. Geoserver is where it says some are
Point fields and the rest are Geometry.

Thing is, I can't force Geoserver to see those as Geometry fields. Sure, I
only use Points anyway, but Geometry works and Point doesn't, and Geoserver
insists that some are one and some are the other. Any way to force it to be
Geometry?

I made the tables using the exact same SQL, by the way. The schemas,
constraints, and permissions are exactly the same. They all enforce the
geometry field to only allow null or "POINT". I even put the same data in
two tables, one that did work and one that didn't, and the results were
unchanged.

--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Using-the-default-values-in-a-new-row-tp6842711p6868012.html
Sent from the geotools-gt2-users mailing list archive at Nabble.com.