Closed zhiyunliu closed 5 years ago
Please write english.
title: Call the stored procedure and report an error when the out parameter is null. i used this way to solve it. is it fine. https://github.com/zhiyunliu/go-oci8/commit/8fd85141081b4c5855a68f3b1fd2de9511160195
This is my modification code. just want to tell you what i changed.
sorry , my english is poor
okay, now i understood what you mean. thank you.
@zhiyunliu Can you please provide an SQL and PL/SQL example of the problem so we can make a test case?
It's incredible that using the new version of oci8 works well. I did not find any inconsistencies in acquisition errors. in my fork version ,it is still working error.
create or replace procedure p_test_output(v_in varchar2, v_in2 number, v_n out number, v_b out varchar2) is begin v_n := 1; end;
@zhiyunliu So there is no issue?
yeah,i suppose so.
well ,i want to known how to fix this in new version also.
there are same in getError.
Are you asking how to fix ORA-01405? If so, did you try running your package in sql plus to see what is going on?
yes,the procedure works fine, but raise error in my fork version.
In your Go code, try changing var pb string
to var pb sql.NullString
and let me know what happens.
raise [ORA-01405] error yet.
i change my project to use the lastest version,so forget the issue now.then i have free time i will find what's the reason. thank you.
我这样解决请帮忙看看是否合理。
https://github.com/zhiyunliu/go-oci8/commit/8fd85141081b4c5855a68f3b1fd2de9511160195#diff-eaeb246e5dfb1f0b15828b3713028f45