DatabaseMetaData.getDatabaseProductVersion should return the DB edition too.

[JSamir]

Is your feature request related to a problem? If so, please give a short summary of the problem and how the feature would resolve it

We have some code that does different stuff depending on the DB being enterprise or standard edition. For oracle we can use getDatabaseProductVersion which returns the edition too, it would be good if sqlserver would to the same.

Describe the preferred solution

Have "Standard/Enterprise Edition" within the version string.

[mprins]

That sounds like a breach of contract https://docs.oracle.com/javase/8/docs/api/java/sql/DatabaseMetaData.html#getDatabaseProductVersion--
You would need to use https://docs.oracle.com/javase/8/docs/api/java/sql/DatabaseMetaData.html#getDatabaseProductName-- for getting the product name

[JSamir]

I would also rather expect the information about the edition to be returned by getDatabaseProductName, I have mentioned the other method only because in case of oracle it is returned by that method.

According to my test none of the methods returns the database edition. Do you get the edition as part of getDatabaseProductName?

[mprins]

but you've asked for a modification of getDatabaseProductVersion and not getDatabaseProductName

as you can see in the code getDatabaseProductName returns a hardcoded stringinstead of return what select @@version produces.

see also https://sqlhints.com/tag/sql-version-to-product-name-mapping/

[JSamir]

I've asked for the modification of getDatabaseProductVersion because oracle is putting the edition information in there already, but I do agree that it should have been getDatabaseProductName all along.

And yes, I already looked up getDatabaseProductName and noticed that it returns a hard coded string.

In any case I would like to have the information about the DB edition, regardless of the method that returns it.

[ulvii]

Is the suggestion to return @@VERSION from getDatabaseProductName()?

[JSamir]

@ulvii Yes.

[ulvii]

Thanks @JSamir , we will look into this.