Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upNumber precision when selecting from dual #907
Comments
lwasylow
self-assigned this
Apr 26, 2019
This comment has been minimized.
This comment has been minimized.
|
In this scenario I think issue is with dbms package as showing precision as zero where allowed is 1..38 we should check if precision is positive and apply then otherwise type mark as number with no precision and scale |
lwasylow
added this to the v3.1.7 milestone
Apr 27, 2019
jgebal
added
the
bug
label
Apr 27, 2019
lwasylow
closed this
in
#908
Apr 27, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
lwasylow commentedApr 26, 2019
•
edited
When running a tests like this
it fails with
ORA-01438: value larger than specified precision allowed for this column ORA-06512: at "UT3.UT_DATA_VALUE_REFCURSOR", line 332 ORA-06512: at "UT3.UT_DATA_VALUE_REFCURSOR", line 380 ORA-06512: at "UT3.UT_EQUAL", line 225 ORA-06512: at "UT3.UT_EXPECTATION", line 26 ORA-06512: at "UT3.UT_EXPECTATION", line 138 ORA-06512: at "UT3.UT_SAMPLE_TEST", line 10This is due to
ut_compound_helper.generate_xmltab_stmtanddbms_sql.describe_columns3for some reason it set max column len to 4 , precision to 0 and scale to -127 when selecting from dual.Solution is if the type is NUMBER then use a precision and scale instead of max_col_len.