[Gvsig_english] gvSIG 1.10 not working properly with PostgreSQL/PostGIS

[Francisco José Peñarrubia]

Hi Klaus.

Yes, it seems a bug (or two). We will try to fix it for 1.12 release. 
Unfortunately, 1.11 is closed and we can't add new features or fix new 
errors for the next release.

Thanks for your help.

Fran.

El 14/01/2011 14:27, Klaus Schaefer escribió:
> The table is actually a very simple one, coming from a point shapefile:
>
> CREATE TABLE st
> (
>    gid serial NOT NULL,
>    "no" character varying(30),
>    latitude character varying(30),
>    longitude character varying(30),
>    "name" character varying(30),
>    altitude character varying(30),
>    mapdate character varying(30),
>    donor character varying(30),
>    active character varying(30),
>    "volume m3" character varying(30),
>    remark character varying(30),
>    photo character varying(254),
>    the_geom geometry,
>    CONSTRAINT st_pkey PRIMARY KEY (gid),
>    CONSTRAINT enforce_dims_the_geom CHECK (st_ndims(the_geom) = 2),
>    CONSTRAINT enforce_geotype_the_geom CHECK (geometrytype(the_geom) =
> 'POINT'::text OR the_geom IS NULL),
>    CONSTRAINT enforce_srid_the_geom CHECK (st_srid(the_geom) = (-1))
> )
> WITH (
>    OIDS=FALSE
> );
> ALTER TABLE st OWNER TO postgres;
> GRANT ALL ON TABLE st TO public;
> GRANT ALL ON TABLE st TO postgres;
>
> -- Index: st_the_geom_gist
>
> -- DROP INDEX st_the_geom_gist;
>
> CREATE INDEX st_the_geom_gist
>    ON st
>    USING gist
>    (the_geom);
>
> And here you can see the data, imported with the plugin (watch the "\" in
> the paths, they create the problem in the gvSIG "layer -->  export to
> PostGIS" function):
>
> http://osgeo-org.1803224.n2.nabble.com/file/n5921663/SamplePostGIS-DB.jpg
>
>

-- 
Fran Peñarrubia
Scolab
www.scolab.es

Asociación gvSIG
www.gvsig.com