Feature/1082 failure when comparing nested objects by lwasylow · Pull Request #1179 · utPLSQL/utPLSQL
added 4 commits
Covers issues of displaying wrong info in diff message for nested objects. Exclude object type from being part of the SQL generation.
…from XML extract causing to fail. Please see #1098 Resolve a situation where a more than two levels of nesting were causing ambiguity on the column name for hash. E.g. <OBJ1><FIRST><VAL><TEST> <OBJ1><SECOND><VAL><TEST> Was taking into hash consideration only parent.
This was linked to issues
…o fact that there was no name for collection columns as part of cursor only data type. Added extra tests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters