Skip to main content
Solved

inconsequential regexp treatment in fme?

  • May 13, 2015
  • 1 reply
  • 10 views

gio
Contributor
Forum|alt.badge.img+15
I find regexp treatment to be inconsequential?

 

 

In stringsearcher this works

 

 

This lets "Bomen" pass, but not "BOMEN" or "menBo"

 

 

But in NullAttributeValueMapper

 

 

 

This lets "Bomen" pass..but also "BOMEN"

 

I suspect because of lack of CASE sensitivity control.

 

(can't use switches in this one).

 

 

 

If i use [^(Bomen)] in the NAM on the other hand it works..and only passes "Bomen".

 

 

Why is that? some regexp flavour-mixing?

Best answer by ebygomm

I know different transformers use different regular expression engines, although doesn't specifically mention which category the attributevaluemappers fall into

 

 

https://knowledge.safe.com/articles/Error_Unexpected_Behavior/Regular-expressions-that-work-in-one-parameter-fail-in-another

 

 
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

ebygomm
Influencer
Forum|alt.badge.img+46
  • Influencer
  • Best Answer
  • May 13, 2015
I know different transformers use different regular expression engines, although doesn't specifically mention which category the attributevaluemappers fall into

 

 

https://knowledge.safe.com/articles/Error_Unexpected_Behavior/Regular-expressions-that-work-in-one-parameter-fail-in-another