-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
getProcedures() does not return SPECIFIC_NAME #2320
Comments
getProcedureColumns also missing the column |
This has been requested before in #448 and #1491. We're hesitant to make these changes as the potential performance impact (as mentioned in #849) would be quite large. An option is to introduce this as an optional change under a connection string option, but then the driver would be in the awkward position where the more compliant option is not the default one. Not to mention the work that would go into developing this option, not just for getProcedures or getProcedureColumns, but for all DatabaseMetadata methods that specify this extra column. For the moment this will be marked as an enhancement, just like #448 and #1491 above, but its not clear when work on a SPECIFIC_NAME column for these methods would take place. |
Driver version
12.6.0.jre11
SQL Server version
mcr.microsoft.com/mssql/server:2022-latest
Client Operating System
JAVA/JVM version
Table schema
?
Problem description
The result of
DatabaseMetaData#getProcedures
does not containSPECIFIC_NAME
column.Expected behavior
The result set should contain the column of
SPECIFIC_NAME
Actual behavior
The column is missing.
Error message/stack trace
Any other details that can be helpful
JDBC trace logs
This is related to #849.
I'm writing a general library depends on the specification and the workaround explained on the issue is not applicable.
The text was updated successfully, but these errors were encountered: