Open matthew-wozniczka opened 7 years ago
Should we use KEY={VALUE}, with a single value instead?
We had discussed this before, and decided to update the spec to make
KEY=VALUE
a special case which was used explicitly for 'informational' keys, IIRC.
Section 3.2.2 (Web-based Authentication Flow with SQLBrowseConnect) says that the driver should return 'informational' keys like
AuthorizationUrl
andAuth_WindowHeight
inOutConnectionString
fromSQLBrowseConnect
.The syntax used is '
KEY
=VALUE
', which actually goes against the documented behaviour (in ODBC 3.8), which says that they must be of the form 'KEY
=?' or 'KEY
={VALUE
(,VALUE
)*}'. The documentation forSQLBrowseConnect
needs to be updated to describe this new feature.