Item10465: more =~ madness
Priority: Urgent
Current State: Closed
Released In: 1.1.3
Target Release: patch
Applies To: Engine
Component: OP_match
Branches: Release01x01 trunk
This expression works on trunk, fails on 1.1.3-beta1:
%STARTSECTION{"test"}%
%QUERY{"'Support.Faq41'/fields[NOT lc(attr)=~'h'].name"}%
%ENDSECTION{"test"}%
With this error: Excess operators (not =) in ''Support.Faq41'/fields[NOT lc(attr)=~'h'].name' at '.name'
Test:
TopicTitle,TopicClassification,Subject,TopicSummary,Extension,InterestedParties,RelatedTopics
--
PaulHarvey - 10 Mar 2011
This might also be my fault and contained only to the foswiki.org 1.1.3-beta1 installation (incorrect application of Sven's =~ fixes to foswiki.org)
--
PaulHarvey - 10 Mar 2011
this might indeed be resolved in the branch - on my system it seems to be ok
I'm hoping we can update f.o to a 1.1.3beta2 and see
--
SvenDowideit - 17 Mar 2011
Added unit tests. As we already fixed a fundamental problem with =~ in a different task, I'm just going to directly close this (unnecessary noise in the release notes for 1.1.3)
--
PaulHarvey - 17 Mar 2011
Sadly the new test doesn't pass on Release01x01, but using
syntaxOnly => 1
does pass.
--
PaulHarvey - 17 Mar 2011
It seems that on Release01x01 the new test (test_match_lc_field) falsely evaluatestoConstant, but I don't know how to debug/fix that. SO I bring this to the attention of Crawford & Sven.
--
PaulHarvey - 17 Mar 2011
Thanks Babar for noticing the difference precedent values for the =~ operator vs trunk. Closing
--
PaulHarvey - 23 Mar 2011
Re-opened to cherrypick a commit missing in trunk,
Item11456
--
PaulHarvey - 20 Jan 2012