Hi Stefan, first of all, excuse for my poor english and thanks for the response.
I have make some new tests on PostGIS-OpenJUMP integration and I get this results: I create a postGIS table from some shapefiles using the postGIS loader shp2pgsql. That script create a table with a field named 'gid' (datatype 'serial') on which is created the primary key of the table. On the field that contains the geometry (named 'the_geom') are created, automatically, three constraint: 1. constraint on SRID 2. constraint on dims of geometry 3. constraint on type of geometry If I created a layer on openJUMP that contains only geometry of the type equal that on postGIS table I can import them successfully in the table (in insert and in overwrite mode). This (for me) is the question. I think that a user couldn't draw on a layer imported from an existing postGIS table a geometry of a different type because he should have an error if updated the table with the new features. Should exist the way to enforce that constraint on a openJUMP layer. Also, when I create a layer on openJUMP, draw some features on it and then save it on postgis table, the table created has the geometry field of type 'GEOMETRY' and only two constraint on this field: 1. constraint on SRID 2. constraint on dims of geometry The data are saved successfully on this postGIS table. Another question: there's a way to draw features M (MULTILINESTRING,MULTIPOLYGON, ..) on a openJUMP Layer? Thanks for the interest. Giuseppe _______________________________________________ jump-users mailing list [email protected] http://lists.refractions.net/mailman/listinfo/jump-users
