-
Notifications
You must be signed in to change notification settings - Fork 186
Exception when comparing collections with utp.ut.expect #1235
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
Comments
Please provide information about your database version and type (SE/EE/XE/Exadata/Cloud/on-prem) |
Hello |
The problem relates to the datatype we use in DBMS_SQL to describe cursor data. On our side, we need to make a fix with dynamic compilation. That should not b a massive change but it will be provided in some next version of utPLSQL. Until then, the short-term solution would be to use object/collection type names that are shorter than 30 characters. |
jgebal, thank you for your answer and recomendation. |
jgebal, should I close the issue or you will close it after the fix ? |
I will close it after a fix. |
Describe the bug
When comparing collections converted to anydata with utp.ut.expect sometimes we get this error, usually it works correctly.
Provide version info
utPLSQL 3.1.12
Information about client software
not applicable
To Reproduce
Run the below script
See the exception:
ORA-06502: PL/SQL: : numeric or value error: character string buffer too small
ORA-06512: на "UTP.UT_DATA_VALUE_ANYDATA", line 98
ORA-06512: на "SYS.DBMS_SQL", line 2146
ORA-06512: на "UTP.UT_CURSOR_DETAILS", line 100
ORA-06512: на "UTP.UT_DATA_VALUE_ANYDATA", line 84
ORA-06512: на "UTP.UT_DATA_VALUE_ANYDATA", line 114
ORA-06512: на "UTP.UT", line 33
ORA-06512: на line 61
Expected behavior
We expect to get collections differences.
The text was updated successfully, but these errors were encountered: