[GROOVY-6612] GroovyRowResult case insensitive inconsistency

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.2.1
• Fix Version/s: 2.3.2, 2.2.3
• Component/s: groovy-jdk, SQL processing
• Labels: groovy
• Assignee: Paul King
• Reporter: Yair Nergaon
• Created: 07/Mar/14 01:11
• Updated: 28/May/14 03:03
• Resolved: 23/May/14 05:15

Description

Looks like GrrovyRowResult property access is not consistent.
The current implementation semantics which basically "says as long as there is one key per case insensitive string the property fetching is case insensitive" does not make sense to me and moreover it is not consistent.
The attached testcase shows the inconsistency. In fact, it is not clear at all what should be the result after the second property assignment.

To overcome this bug I have AOP the propertySet and before any settings I removed the previous one (if exists) ensuring no than one String case insensitive key at the time. Without this my Sql row processing is not deterministic.
Thanks in advance,
Yair