Output parameter stops work after first commit [ODBC49] #50
Comments
|
Commented by: Vladimir Kozlov (vkozlov) This is a simple test program written on C# to demonstrate this behavior. |
Modified by: Vladimir Kozlov (vkozlov)Attachment: Program.cs [ 11140 ] |
Modified by: @alexpotapchenkoassignee: Vladimir Tsvigun [ praktik ] => Alexander Potapchenko [ lightfore ] |
Modified by: @alexpotapchenkostatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.0 Beta [ 10043 ] |
|
Commented by: pabloj (pabloj) Alexander, would you mind adding a quick comment when closing bugs? I see this is fixed in CVS but not in available builds (as of 01/11/2008), am I right? |
|
Commented by: @alexpotapchenko This fix (and some others) will be included into 148 Beta build (it is possible that this build will be last before RC1). |
Modified by: @alexpotapchenkostatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Vladimir Kozlov (vkozlov)
Attachments:
Program.cs
Under http://ADO.NET OdbcCommand, if we make subsequent calls of a stored procedure via ODBC driver (each call in a new transaction), the output parameters returns correctly only at first call. Once the first call was executed, the output parameters in next transaction returns empty.
Same calls using native .NET provider works correctly.
Commits: 0692110 612929d
The text was updated successfully, but these errors were encountered: