Is it possible to add the index/PK/not null constraint creation feature on User Attributes to FeatureWriter when the Format is a database? Just like in the writers.
Archived
FeatureWriter: Index management on User Attributes
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+26- Contributor
In general: If the FeatureWriter is going to replace the writers in the future, it should behave like the writers and have the same possibilities.
+59- Safer
Is there still anything missing and, if so, from which formats? I just checked PostGIS, SQL Server, Informix, CouchDB and they all have the same options in the FeatureWriter as the plain writer
But that's FME2016.1 so it may be different to what you were looking at.
eg
'
So perhaps all is good for you now?
+22- Supporter
Yes, that's great now :) We used 2016.0 in March, this is why there was no Index column.