Skip to main content
  • EN

Heya FME specialists, can you please give a thought on the next issue:

Created a new table in PostGIS with FME from shape, using the PostGIS writer. (see 00_initiate.fmw)

 

Point feature, attributes pkey and a, b, c with values. Insert, drop and create.

Updated this table with the PostGIS writer. (see 01_update.fmw)

 

Point feature, pkey, and only a, b with values. Update based on pkey, use existing.

The problem is: We decided to maintain attribute c with QGIS directly in PostGIS but kept editing the geometry and attributes a and b in the shape. I deleted the attribute c in the writer assuming it wouldn't write it anymore to the database. That assumption appeared to be wrong and to prevent updating attribute c I had to use an AttributeKeeper in front of the PostGIS writer. My problem solved but curious if this is a DB writer syntax or a bug?

Using FME Desktop 2016.1.0.1 on Windows 7. Uploaded workbenches in zip for reproduction.

Thanks!

Do you have the log file for the incorrect behaviour? That may tell us what SQL statement is being used to update the data. It would be interesting to see if that attribute is part of it. Either way I will file a report to our developers and see if they think it's a bug that needs fixing.

 

 

Filed with development as PR#71568

 

 

Do you have the log file for the incorrect behaviour? That may tell us what SQL statement is being used to update the data. It would be interesting to see if that attribute is part of it. Either way I will file a report to our developers and see if they think it's a bug that needs fixing.

 

 

Not sure what log you need exactly? The FME log with debug on doesn't show the update statement.

 

 

Filed with development as PR#71568

 

 

This sounds oddly familiar, I have a feeling I've already filed this a long time ago...
Not sure what log you need exactly? The FME log with debug on doesn't show the update statement.

 

 

Sometimes it does, but I guess sometimes it doesn't. Oh well. We'll see what the developers say.

 

 

Hi @mark2atsafe, is it possible to have information about the resolution of this trouble ?

I think I have something similar with the last version of FME (2019.2) but not in the previous version (2019.1).

Thank's

It’s very late, I know, but I can confirm that this issue is fixed. 2024.2 is the version containing the fix.

Reply


Community Stats

30,351
Posts
115,341
Replies
38,080
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.