Question

PostGIS dynamic writer forces lowercase attribute (column) names

drejkzet

As is stated in the title. However I need column names to be created exactly as they are, for example I have incoming attribute "OGC_ANGLE.uom" and even though I have Lower Case Attribute Names unchecked,

tables in database have column names are created lowercase ("OGC_ANGLE.uom" becomes ogc_angle_uom) - this is a problem, if I read those tables and try to use xsd to create gml again, as these attributes are unknown to the xsd, therefore failing creation of the gml. I could manually rename those columns, however I would need to rename those columns every time xsd file changes, which is why I need to do this dynamically in the first place, as those xsd files are going to be updated quite often...

 

And it seems that the dynamic PostGIS writer ignores Table Qualifier, it always creates tables in default schema, unless I specify schema in Table Name (schema.@Value(fme_feature_type))

11 replies

H
Badge +2

Hi @drejkzet,

Sorry that you are running into this issue. This is a known problem where when you use the PostGIS writer to write dynamically it acts as though the 'Lower Case Attribute Names' box is always checked. I have assigned this Question to the issue so should a fix be put in place you will be notified here.

david_r
Rank
Userlevel 4

Hi @drejkzet,

Sorry that you are running into this issue. This is a known problem where when you use the PostGIS writer to write dynamically it acts as though the 'Lower Case Attribute Names' box is always checked. I have assigned this Question to the issue so should a fix be put in place you will be notified here.

Hi @hollyatsafe, we're still running into this issue with FME 2020.0.3 build 20252. Do you have a timeline for when this will be fixed?

H
Badge +2

Hi @hollyatsafe, we're still running into this issue with FME 2020.0.3 build 20252. Do you have a timeline for when this will be fixed?

Hi @david_r,

Upon review this bug is currently blocked by work that needs to go into a separate but related issue. I have raised this with one of our FME Desktop Product Owner's to try and get the ball rolling and she is going to take a look and determine what is needed for us to be able to implement a fix.

 

 

Hopefully I'll have some more information for you on this shortly.

arthur_bazin
Rank
Badge +1

FME 2021.1 and the bug is always here.

Thats a really big bug for me as it is nearly impossible to use dynamic feature type with PostgreSQL or PostGIS. Dynamic features and schema are one of the best feature of FME, really sad to have this bug since so long.

@hollyatsafe​ have you some news about this trouble ?

Thank you

danminneyatsaf
Rank
Userlevel 2
Badge +10

FME 2021.1 and the bug is always here.

Thats a really big bug for me as it is nearly impossible to use dynamic feature type with PostgreSQL or PostGIS. Dynamic features and schema are one of the best feature of FME, really sad to have this bug since so long.

@hollyatsafe​ have you some news about this trouble ?

Thank you

Hi @arthur_bazin​,

Unfortunately, the bug is still blocked by various issues that are preventing it from being fixed. Issues to do with dynamic mode can be quite complex and in this case, the issue expands beyond the PostgreSQL and PostGIS format, increasing the effort needed to solve the issue. At the moment, we're still hoping to get a fix out sometime in the future, but I can't give a concrete date.

 

Also, I have made note of your concerns on the bug report so you will be notified when we have an update.

arthur_bazin
Rank
Badge +1

Hi @arthur_bazin​,

Unfortunately, the bug is still blocked by various issues that are preventing it from being fixed. Issues to do with dynamic mode can be quite complex and in this case, the issue expands beyond the PostgreSQL and PostGIS format, increasing the effort needed to solve the issue. At the moment, we're still hoping to get a fix out sometime in the future, but I can't give a concrete date.

 

Also, I have made note of your concerns on the bug report so you will be notified when we have an update.

Thanks for your quick answer.

It's a really bad news as I was hoping that this bug could be resolved quickly.

 

Thank you for the notification.

 

Have a nice day.

arthur_bazin
Rank
Badge +1

FME 2023.0.0.3 and the bug is always there...

 

New brand design, higher prices (that climb to summit) but the same mecanics...

Really desapointed that FME is still not fully compatible with PostgreSQL witch is the minimum required for any GIS software in 2023 (maybe since 5 or 10 years now).

 

I understand that there may be some complex things behind this problem but this is really anoying and a minimum when you work with Oracle and PostgreSQL...

 

If you can put a little poke on this issue that will be really appreciated on our side.

 

Thank's !

Best regards !

danminneyatsaf
Rank
Userlevel 2
Badge +10

FME 2023.0.0.3 and the bug is always there...

 

New brand design, higher prices (that climb to summit) but the same mecanics...

Really desapointed that FME is still not fully compatible with PostgreSQL witch is the minimum required for any GIS software in 2023 (maybe since 5 or 10 years now).

 

I understand that there may be some complex things behind this problem but this is really anoying and a minimum when you work with Oracle and PostgreSQL...

 

If you can put a little poke on this issue that will be really appreciated on our side.

 

Thank's !

Best regards !

Hey @arthur_bazin​ just wanted to give you an update on the progress with resolving the bug. As mentioned before, the bug was blocked by various other issues that first needed to be resolved to get this functioning correctly. Fortunately, these blocking issues have now been resolved which means the team can move forward with resolving this issue.

 

I've reached out to our FME Engine product manager to share you concerns as well. This bug has long since been one we've looked forward to resolving and I know we're one step closer to getting there now that it isn't blocked by that other issue. We'll keep you updated throughout the process and let you know when we you can expect to see the fix for the issue released.

 

Thanks again for your patience and generous feedback!

arthur_bazin
Rank
Badge +1

Hey @arthur_bazin​ just wanted to give you an update on the progress with resolving the bug. As mentioned before, the bug was blocked by various other issues that first needed to be resolved to get this functioning correctly. Fortunately, these blocking issues have now been resolved which means the team can move forward with resolving this issue.

 

I've reached out to our FME Engine product manager to share you concerns as well. This bug has long since been one we've looked forward to resolving and I know we're one step closer to getting there now that it isn't blocked by that other issue. We'll keep you updated throughout the process and let you know when we you can expect to see the fix for the issue released.

 

Thanks again for your patience and generous feedback!

Thank you very much for your answer and for this great news.

Hope to see this issue resolved in a few times :-D

 

Best regards from France !

felipeverdu
Rank
Badge +8

Hi @danminneyatsaf​ 

I would like to be updated on this issue since I have the same problem.

Br

Felipe Verdú

danminneyatsaf
Rank
Userlevel 2
Badge +10

Hi @danminneyatsaf​ 

I would like to be updated on this issue since I have the same problem.

Br

Felipe Verdú

Hi @felipeverdu​ we'll make sure to update you (as well as everyone else) about this issue when it's resolved.

I'm aware of some upcoming changes in FME 2024.0 that will allow users to un-check the Create Generic Spatial Columns parameter and the Lower Case Attribute Names parameter with a normal dynamic PostGIS/PostgreSQL Writer.

 

The fix mentioned above does not include the FeatureWriter unfortunately as that still being resolved. Since I don't see it here yet, the tracking number for this issue/bug is FMEENGINE-9157.

Reply


Community Stats

28,684
Posts
109,413
Replies
36,542
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.