Skip to content

Feature/1082 failure when comparing nested objects #1179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 9 commits into from
Jan 29, 2022

Conversation

lwasylow
Copy link
Member

@lwasylow lwasylow commented Jan 26, 2022

Fixing issue where code was failing on the nested objects due to "object" type being pulled into dynamic SQL as datatype to extract into.

Fixing issue when null value was passed to get_hash function causing compare to fail

Address a possible scenario when more than 2 levels of nesting for same objects caused ambiguity of the column name.

Closing #1082
Closing #1098
Closing #1083

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.
…o fact that there was no name for collection columns as part of cursor only data type.

Added extra tests.
@lwasylow lwasylow linked an issue Jan 26, 2022 that may be closed by this pull request
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@jgebal
Copy link
Member

jgebal commented Jan 28, 2022

Let me have a deeper look into that PR before I approve it

@jgebal
Copy link
Member

jgebal commented Jan 28, 2022

I've reviewed the PR. It addresses all 3 issues.
Brilliant work @lwasylow 👌 👍

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@lwasylow lwasylow requested a review from jgebal January 29, 2022 19:42
@jgebal jgebal added this to the 3.1.12 milestone Jan 29, 2022
@lwasylow lwasylow merged commit 4d55bf4 into develop Jan 29, 2022
@lwasylow lwasylow deleted the feature/1082_failure_when_comparing_nested_objects branch January 29, 2022 21:08
@jgebal jgebal added the bugfix label Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fails when a grand child nested type have NULL Unreadable & misleading results when comparing nested objects Failure when comparing nested objects
3 participants