Closed viney closed 10 years ago
big.Int or NumersAsStrings?
Ran into this issue as well. What I noticed is that the problem seems to lie in param processing. E.g.:
if you have IDs 1, 2 1234567890123
SELECT * FROM tb will return all results
SELECT * FROM tb WHERE ID = :1 and if you put 1234567890123 as the param, it fails.
What is the type of tb.id ? string or number?
2014-11-03 17:43 GMT+01:00 Qian Qiao notifications@github.com:
Ran into this issue as well. What I noticed is that the problem seems to lie in param processing. E.g.:
if you have IDs 1, 2 1234567890123
SELECT FROM tb will return all results
SELECT FROM tb WHERE ID = :1 and if you put 1234567890123 as the param, it fails.
— Reply to this email directly or view it on GitHub https://github.com/tgulacsi/goracle/issues/17#issuecomment-61507078.
Sry, forgot to mention, it's number
I can reproduce it with in-memory tables: https://github.com/tgulacsi/goracle/blob/ora-1458/oracle/cursors_test.go#L24
Just tested ora-1458 branch using number 22544687786605, which is something I have in one of my production systems that broke master, the fix works like a charm.
Thanks for the prompt reply and fix!