Skip to main content
Open

Respecting field name length limitations and reserved keywords per feature write

Related products:Integrations
siennaatsafe
gbj1717
travg
mb_fdfa
spahlinger
  • siennaatsafe
    siennaatsafe
  • gbj1717
    gbj1717
  • travg
    travg
  • mb_fdfa
    mb_fdfa
  • spahlinger
    spahlinger

mb_fdfa
Participant

***Note from Migration:***

Original Title was: Respecting field name length limitations and reserved keywords per feature writer type


1) Field name length

As the maximum length of a field name in various formats is known (databases, shapefile, etc), it would be very helpful if FME Writers validated this on attributes entered.

https://desktop.arcgis.com/en/arcmap/latest/manage-data/gdbs-in-sql-server/enterprise-geodatabase-limits.htm
https://desktop.arcgis.com/en/arcmap/latest/manage-data/gdbs-in-oracle/enterprise-geodatabase-limits.htm
https://pro.arcgis.com/en/pro-app/help/data/geodatabases/manage-file-gdb/file-geodatabase-size-and-name-limits.htm

2) DB Keywords

In a similar fashion, there are reserved keywords which can't be used as field names in many formats - this could also be validated on writers.
https://docs.microsoft.com/en-us/sql/t-sql/language-elements/reserved-keywords-transact-sql?view=sql-server-ver15

Error messaging for this in the translation log could also be clearer.

0 replies

Be the first to reply!

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings