Skip to main content
Question

SQLExecutor error exposing multiple attributes

A
Forum|alt.badge.img+1

Hi, I am using FME Desktop version: FME(R) 2020.1.1.1 (20200817 - Build 20614 - WIN64)

 

Using the SQLExecutor (version 9) against an Oracle Spatial Table, I am running  a SQL statement such as below:

select "LINE", "COLOUR" from "SCHEMA"."TABLENAME"

 

 This statement 'runs successfully' when tested but when I expose multiple attributes using the 'Attributes to  Expose' field, this does not work and a single attribute with all the field names concatenated with a comma is being output:

 

Capture If I expose a single attribute only then the output is correct.  Is this a bug with this version of FME Desktop 2020.1 and or SQLExecutor Version 9, as it does not happen with previous versions of FME Desktop and SQL Executor?

Thanks!

5 replies

david_r
Evangelist
  • david_rEvangelist
  • March 18, 2021

This somehow rings a bell, but I cannot remember in which post I've seen this before. Since it's Oracle everything will be interpreted as upper case by default, so you could try to skip the quotation marks and see if that makes a difference? You could perhaps also try using a separate AttributeExposer.

ebygomm
Influencer
Forum|alt.badge.img+31
  • ebygommInfluencer
  • Influencer
  • March 18, 2021

What happens if you use? 

select LINE, COLOUR from "SCHEMA"."TABLENAME"

 

A
Forum|alt.badge.img+1
  • aquamarine
  • Author
  • March 18, 2021
ebygomm wrote:

What happens if you use? 

select LINE, COLOUR from "SCHEMA"."TABLENAME"

 

I've tried that with no luck as well. But I've just found that if I put double quotation marks around each attribute name in the 'Attributes to Expose' field, it does work!

 Capture2Do you know if this is a bug and will be fixed in future releases of FME?

chrisatsafe
Contributor
Forum|alt.badge.img+2
  • chrisatsafeContributor
  • Contributor
  • March 22, 2021
aquamarine wrote:

I've tried that with no luck as well. But I've just found that if I put double quotation marks around each attribute name in the 'Attributes to Expose' field, it does work!

 Capture2Do you know if this is a bug and will be fixed in future releases of FME?

Hi @aquamarine​,

 

Interesting one. I just tried this in FME 2021 build 21302 and it doesn't appear to have the same issue - no quotes needed around the attribute names in the Attributes to Expose parameter. Could you try in the latest release to see if the issue is resolved for you? If not, our support team could definitely take a closer look into this with you. If it is not resolved in the latest release please get it touch with our support with this info: https://community.safe.com/s/article/general-troubleshooting-gathering-system-informati

A
Forum|alt.badge.img+1
  • aquamarine
  • Author
  • March 23, 2021
aquamarine wrote:

I've tried that with no luck as well. But I've just found that if I put double quotation marks around each attribute name in the 'Attributes to Expose' field, it does work!

 Capture2Do you know if this is a bug and will be fixed in future releases of FME?

Thanks @chrisatsafe​ . As soon as I install FME 2021 I will check this out!

Reply


Helpful Members This Week

Community Stats

30,944
Posts
117,265
Replies
38,743
Members

Latest FME

Terms & ConditionsCookie settings

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
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.