Todo: For the Postgres / PostGIS writers add the option to make an added index unique or primary
Why: Having the ability to have FME create indexes on created tables is great. However many GIS applications need a primary key, or unique index to insure that only one item is updated, or selected with that key. Adding the option to make the index unique saves a manual step in creating an pk or unique index for a table afterward.
+1Isn't this functionality available in FeatureWriter? Set Attribute Definition in User Attributes to manual and you can change the Index value to 'Primary Key.' I presume that is doing what you need? It just worked for me writing into Postgres, anyway.
I would like to let the postgis database create the unique serial primary key for me.
Manually setting the primary key to some (presumably) unique value is perfect when you have a unique value that links back to the original data source. And some other cases. Not so when the sole function of the primary key is to exist, so other applications can use it for sorting, batch-processing N features at a time and so on.
One prime example: Serving WFS through Geoserver on top of a postgis. Geoserver will not complain about it - but QGIS will not be able to use the WFS services if the primary key doesn't exist and is exposed through geoserver.
For this use case, having the database auto increment the primary key is the obvious way to do it. And it would be REALLY nice if the postgis/postgresql writer had this option available.
+45I believe it will do this already as long as you set the field type to serial. From the R+W doc:
serialThis type is used to represent an auto incrementing four-byte integer. The range is 1 to 2147483647. This is similar to specifying an integer column that has default values to be assigned from a sequence generator. It also has a NOT NULL constraint applied to it.
+7
+15Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
