[
https://issues.apache.org/jira/browse/DERBY-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466112
]
Saurabh Vyas commented on DERBY-2243:
-------------------------------------
I looked into the code and found that
DatabaseMetaData.supportsANSI92EntryLevelSQL() is implements in different way
in Embedded and Network-Client mode.
In embedded mode EmbedDatabaseMetaData implements DatabaseMetaData & it returns
false for various functions including supportsANSI92EntryLevelSQL() which is
incorrect. Whereas for network mode, NetDatabaseMetaData implements
DatabaseMetaData & it returns true for supportsANSI92EntryLevelSQL().
I crossed check it with MySql code & found that it also return true (which is
expected ) for supportsANSI92EntryLevelSQL().
Same is the case with DERBY-2244
(https://issues.apache.org/jira/browse/DERBY-2244) & it returns false for
supportsExpressionsInOrderBy() which is incorrect as derby does supports Order
By Clause.
> DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded,
> true for client driver
> -------------------------------------------------------------------------------------------------
>
> Key: DERBY-2243
> URL: https://issues.apache.org/jira/browse/DERBY-2243
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.1.6, 10.2.2.0, 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Saurabh Vyas
> Priority: Minor
>
> Since this method is returning the support level of SQL it must be consistent
> across the drivers.
> Probably need some investigation as to which is correct, most likely 'true'.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
