Skip to main content
Question

Can I set "lower case Table Name" in PostGIS writer parameters, produced with "generate workspace" workaround


Forum|alt.badge.img

Hi. I want to transform data from Oracle spatial to PostGIS. There are over 100 classes to transform. That's why I go with the option "generate workspace". For the writer I choose a PostGIS connection. In the Parameters I have to click the option "lower case attributs name". The same I need for the table name. If the table name is in uppercase letter, I'm not able to open the PostGIS database anymore. If I manualy set it in lower case letter, it works. But there are over 100 writers. Is there a posiblitity to set that generaly? To choose the function "import feature tye" is no option. In this case there is a lower case table name, but reader and writer attributes doesn't finde eache other.

5 replies

chrisatsafe
Contributor
Forum|alt.badge.img+2
  • Contributor
  • June 29, 2021

Hi @Adrian Holzer​ ,

You should be able to achieve this using a dynamic workspace.

 

The table name from your Oracle Spatial database will be stored in the fme_feature_type format attribute. Check out the Dynamic Workflows: Destination Schema Contains Different Feature Type Names article for how to accomplish this :)


Forum|alt.badge.img
  • Author
  • July 1, 2021

thanks for answering. fme_feature_type delivers the value in uppercase letter as well. seems to be an issue for years: https://community.safe.com/s/question/0D54Q000080h5XQSAY/lowercase-postgis-table-names


Forum|alt.badge.img
  • Author
  • July 1, 2021

I just saw your link for Dynamic Workflows. mybe that works. will update you.


Forum|alt.badge.img
  • Author
  • July 8, 2021

yes! with the dynamic Workflow, the fme_feature_type format attribut and the StringCaseChanger it runs successfully. thank's for the help.


chrisatsafe
Contributor
Forum|alt.badge.img+2
  • Contributor
  • July 8, 2021
spirou01 wrote:

yes! with the dynamic Workflow, the fme_feature_type format attribut and the StringCaseChanger it runs successfully. thank's for the help.

Great, thanks for the update. Yes the case for the value of the fme_feature_type format attribute is dependent on the source table name.

 

Glad you got it working using that article as a reference.


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