-
-
Notifications
You must be signed in to change notification settings - Fork 173
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
Querying fields of type NUMBER(20,0) causes ORA-03120 #418
Comments
please share example code to test |
Yeah we're working on it. |
Enclose this column with ROUND(...) is a workaround I use for this issue |
last version v2.7.16 fix some number decoding please try again and see if issue fixed |
Sorry got side tracked on this. I'll try
…On Fri, 25 Aug 2023, 00:59 Samy Sultan, ***@***.***> wrote:
last version v2.7.16 fix some number decoding please try again and see if
issue fixed
—
Reply to this email directly, view it on GitHub
<#418 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALKLW3G532QF2MHUVFXX2TXW7MGTANCNFSM6AAAAAA3C6JODM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are storing pretty large numbers, yet still in the 64bit range.
When performing a SELECT them over them (they are stored in a NUMBER(20,0) field) we get
ORA-03120: two-task conversion routine: integer overflow
We're currently debugging it to try to give more information, but we thought you should know and maybe have an idea.
The text was updated successfully, but these errors were encountered: