Correct sequence value
Opened this issue · 0 comments
chpicone commented
We found that after the data migration process the sequence of the Primary Key of each tables is 0, even if the tables contains data.
We need to align (using setval) the value of the sequence accordingly to the max valuef of the objectid filed (+1).
Otherwise when we try to add new feature (eg using WFS) GeoServer raises an exception because the violtaion of PK.