Calling stored procedure directly #547
Conversation
…nd inserts data multiple times
…ad to see if it contains return value
…oredProcedure # Conflicts: # src/main/java/com/microsoft/sqlserver/jdbc/SQLServerPreparedStatement.java
|
I also added the fix for removing metadata lookup for named parameters. This will break the existing applications that use a mix of named and index parameters. If we need to use named parameters to get the output parameters, we need to register the parameter with name values: and then call: Registering output parameter with name and using indexes to retrieve them, however, still works. |
# Conflicts: # src/main/java/com/microsoft/sqlserver/jdbc/Parameter.java # src/main/java/com/microsoft/sqlserver/jdbc/SQLServerCallableStatement.java # src/main/java/com/microsoft/sqlserver/jdbc/SQLServerConnection.java # src/main/java/com/microsoft/sqlserver/jdbc/SQLServerPreparedStatement.java # src/main/java/com/microsoft/sqlserver/jdbc/SQLServerResource.java # src/main/java/com/microsoft/sqlserver/jdbc/SQLServerStatement.java # src/main/java/com/microsoft/sqlserver/jdbc/dtv.java # src/test/java/com/microsoft/sqlserver/jdbc/AlwaysEncrypted/CallableStatementTest.java
|
Hello mssql-jdbc team, can you please let me know when this will be merged and released? |
|
Hi @praskutti , |
Thanks @ulvii . I coded a usable workaround for our requirement (to create a generic method for SQL Server proc calls that would avoid extra metadata lookups). I thought this PR would solve it, but because it will take time to release, we will roll with our method. I will post the code-sample soon. |
|
This is still being worked on #2154. |
calling stored procedure directly instead of wrapping it around
exec sp_executesql.Not to be merged yet. Opening this pull request for discussion and improvement.
Notice that this still does not have the push for avoiding the metadata lookup with named params. Will be adding that soon to the same pr in another commit.