Skip to content
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

getFunctionColumns() is missing SPECIFIC_NAME column #849

Closed
Impakt opened this issue Oct 24, 2018 · 6 comments
Closed

getFunctionColumns() is missing SPECIFIC_NAME column #849

Impakt opened this issue Oct 24, 2018 · 6 comments
Projects

Comments

@Impakt
Copy link

Impakt commented Oct 24, 2018

according to the Javadocs the getFunctionColumns method is supposed to return a column called SPECIFIC_NAME, but the driver doesn't include it, see here

@cheenamalhotra
Copy link
Member

HI @Impakt

We will investigate the missing column and get back to you soon!

@cheenamalhotra cheenamalhotra added this to Under Investigation in MSSQL JDBC Oct 24, 2018
@ulvii
Copy link
Contributor

ulvii commented Nov 1, 2018

Hi @Impakt ,

I looked into the issue and agree that the returned result set does not contain SPECIFIC_NAME column when it is supposed to.

Please note that SQL Server function names are unique within their schema and FUNCTION_NAME is always the same as SPECIFIC_NAME. For this reason, sp_sproc_columns (SQL Server procedure that gets invoked when you call getFunctionColumns) does not return SPECIFIC_NAME column in the result set. Would using FUNCTION_NAME instead of SPECIFIC_NAME resolve the issue for you?

I also investigated if the driver can duplicate FUNCTION_NAME column and append it to the result set as SPECIFIC_NAME. To achieve this, the driver would have to create a temporary table to join the output of sp_sproc_columns with the new SPECIFIC_NAME column, which obviously would result in a performance/memory overhead to get redundant information.

Please let us know what you think.

@Impakt
Copy link
Author

Impakt commented Nov 3, 2018

We changed our code to not assume that the 'column' would be there. It sounds like a lot of work to add the column to the result set so maybe just leave it out

@ulvii
Copy link
Contributor

ulvii commented Nov 5, 2018

Hi @Impakt ,

Glad you could find a workaround. Please let us know if you have any other questions.

@ulvii ulvii closed this as completed Nov 5, 2018
MSSQL JDBC automation moved this from Under Investigation to Closed Issues Nov 5, 2018
@onacit
Copy link

onacit commented Feb 5, 2024

getFunctions() also misses the column.

@onacit
Copy link

onacit commented Feb 5, 2024

The SPECIFIC_NAME is important that it could(should) be uses the uniqueness of the result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
MSSQL JDBC
  
Closed Issues
Development

No branches or pull requests

4 participants