SS wrote: >Peppe, >I'm not a PostGIS user, so be patient with me.
>You wrote: "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." There is options in the QA-tools for denying certain feature types. That could be used prior to updating PostGIS-tables. It might still be good to have some kind of 'Layer properties' selection where these constraints could be set beforehand. It would prevent problems also if user knows from the very beginning that data are to be stored to shape files. I think that JUMP can not make the decision but it must be the user. I can well imagine that someone would like to to read data from 'single geometrytype' source like PostGIS or WFS server, but still add own features of other type and store the result to formats like JUMP-GML or MapInfo tab supporting mixed geometry types. -Jukka Rahkonen- _______________________________________________ jump-users mailing list [email protected] http://lists.refractions.net/mailman/listinfo/jump-users
