Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Error when using "ut.expect().to_equal" when comparing cursors (3.1.4) #870

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.

Sign up for GitHub

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

Jump to bottom
Closed
vdeG123 opened this issue Mar 22, 2019 · 4 comments
Closed

Error when using "ut.expect().to_equal" when comparing cursors (3.1.4) #870

vdeG123 opened this issue Mar 22, 2019 · 4 comments

Comments

@vdeG123
Copy link

vdeG123 commented Mar 22, 2019

I installed version 3.1.4 2 days ago.
I notice that the framework is throwing an error when trying to compare two cursors with ut.expect().to_equal.

Here's the error stack:
ORA-00904: "UTPLSQL"."UT_COMPOUND_DATA_HELPER"."GET_HASH": invalid identifier
ORA-06512: at "UTPLSQL.UT_DATA_VALUE_REFCURSOR", line 317
ORA-06512: at "UTPLSQL.UT_DATA_VALUE_REFCURSOR", line 365
ORA-06512: at "UTPLSQL.UT_EQUAL", line 225
ORA-06512: at "UTPLSQL.UT_EXPECTATION", line 26
ORA-06512: at "UTPLSQL.UT_EXPECTATION", line 138
ORA-06512: at "XXX.XXX", line 170

I had to add UT_COMPOUND_DATA_HELPER in the create_synonyms_and_grants_for_public.sql script to make it work.

Thanks!
@pesse
Copy link
Member

pesse commented Mar 22, 2019

Hey @vdeG123 ,
can you try it with 3.1.5 and check if it's solved there?

@lwasylow
Copy link
Member

We will look into this and comeback. Thanks for reporting that.

@lwasylow
Copy link
Member

Hey @vdeG123
Can you share a test case you running ? I assume data types in cursor are not standard ? XML or CLOB etc ?

@vdeG123
Copy link
Author

vdeG123 commented Mar 22, 2019

Exactly, the cursor is a SELECT on one column, and this column is a CLOB.

@lwasylow lwasylow mentioned this issue Mar 22, 2019
Merged
@lwasylow lwasylow reopened this Mar 22, 2019
@lwasylow lwasylow mentioned this issue Mar 22, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lwasylow @pesse @vdeG123