Hi there.
I get "ORA-01006: bind variable does not exist" in Direct mode, if I reuse a bind variable in a insert-statement with a returning parameter.
E.g.:
"insert into scott.emp e(e.empno, e.ename) values (:p1, :p2 || :p3 || :p3) returning e.empno into :ret"
Parameter P3 ist added only once to the Command.Parameters.
-> In Direct mode I get ORA-01006. Otherwise not.
-> Without the returning clause/parameter. The statement executes successfully.
-> Without appending :p3 a second time, the statement executes successfully.
I found this problem while testing version 7.0.17. I have no idea if this occurs in earlier versions.
Regards,
Matthias
Multiple usage of bind variables
-
- Devart Team
- Posts: 2420
- Joined: Wed 02 Nov 2011 09:44
Re: Multiple usage of bind variables
We have reproduced the issue. We will investigate it and notify you about the results as soon as possible.
-
- Devart Team
- Posts: 2420
- Joined: Wed 02 Nov 2011 09:44
Re: Multiple usage of bind variables
We have fixed the bug with the multiple usage of the same parameter in the query containing returning in the direct mode. We will post here when the corresponding build of dotConnect for Oracle is available for download.
-
- Devart Team
- Posts: 2420
- Joined: Wed 02 Nov 2011 09:44
Re: Multiple usage of bind variables
The new build of dotConnect for Oracle 7.1.40 is available for download now!
It can be downloaded from http://www.devart.com/dotconnect/oracle/download.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?t=24522
It can be downloaded from http://www.devart.com/dotconnect/oracle/download.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?t=24522
-
- Posts: 12
- Joined: Fri 22 Jan 2010 15:39
Re: Multiple usage of bind variables
Thank you Pinturiccio.
I can confirm: with the new build 7.1.40 it works as expected.
I can confirm: with the new build 7.1.40 it works as expected.