[GEODE-7694] PdxType comparison should favor typeId rather than class name

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.12.0
• Component/s: native client
• Assignee: Ernest Burghardt
• Reporter: Blake Bender
• Created: 13/Jan/20 19:47
• Updated: 31/Mar/20 18:34
• Resolved: 02/Mar/20 20:54

Description

The `operator<` method of PdxType in the native client simply compares the class names, which is incorrect and leads to the fact that, in NC, you cannot currently have two separate PDX types with the same class name.  The comparison should favor type ID first, then if both type IDs are 0 (true for local regions), fall back to class name.  This will still fail for local regions in the scenario where class names are the same, but it's much, much better than we have now.

Issue Links

• links to: GitHub Pull Request #572