Hi,
I wonder how can I update a postgresql postgis database before the
following scenario:
Always worked with shape files and update them used copy / paste between
files.
Now, think about creating a database in PostgreSQL and would like to
continue using copy / paste to update polygons, but in my
tl;dr: Have you tried QGIS?
What were you using to copy/paste before? I didn't think straight
editing of the DBaseIII files directly was a sane thing to do, as
they're linked up with the shape and shape-index files.
PostGIS is just a PostgreSQL database, so any editor that can allow you
to
Yes, I'm using QGIS. I agree, if I make a table in the database with the
same structure the shape file is simple. The copy / paste works perfectly.
But my question is how to update for example the blocks table, using the copy
/ paste, since the database structure is different.
For example, if I
Ok,
I have a shape file with the following structure.
Shape file, columns:
town code;
town description;
Neighborhood code;
name of the neighborhood;
block code;
Street code;
street name;
Using the How to Copy / paste a geometry from shape file to postgis with
follow structure:
Cities table
I guess I'm still not fully understanding the problem. I don't understand what
problem the normalization is causing you. You shouldn't need to duplicate the
rows in different tables when you duplicate one in another table.
To edit fields in QGIS you need to enable editing on the layer and then
maintaining your data model is easy to do with triggers.
About copy / past.
Sorry this just doesn't make much sense to me.
You can import shapefile into postgres if it is the question.
You can also use trigger on the import table to fill you rmodel with the
imported data.
Cheers,
Rémi-C
Very good !!
based on Remi's advice and some adjustments, it worked!
Now the table is updating using the SQL Editor or the Qgis.
Thank you all!
2015-04-18 16:19 GMT-03:00 Rémi Cura remi.c...@gmail.com:
Ok, this is totally a postgres question then.
First you create your data model (here it
Glad it works ^^
A note for archive : this solution won't be super-efficient.
This looks like a textbook case for using the postgres rule system.
A simpler solution would be to switch to statement trigger (as opposed ot
row trigger) if you care about it, but it may be trickier to write.
Cheers,
