Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Invalid MSSQL datasource after update from 5.0.1.42 to 5.0.1.67

Description

This datasource was working fine with Lucee 5.0.1.42:

<data-source allow="511" blob="false" class="com.microsoft.sqlserver.jdbc.SQLServerDriver" clob="true" connectionLimit="100" connectionTimeout="1" custom="DATABASENAME=contens5_dev&amp;sendStringParametersAsUnicode=true&amp;SelectMethod=direct" database="contens5_dev" dbdriver="MSSQL" dsn="jdbc:sqlserver://{host}:{port}" host="srv-mssqlcore" metaCacheTimeout="60000" name="contens5_dev" param-delimiter="&amp;" param-leading-delimiter="?" param-separator="=" password="*****" port="1434" storage="false" username="dbadmin" validate="true"/>

After updating to 5.0.1.67 the validation fails, see attachment

Nothing relevant in the logs

Environment

Windows

Attachments

1
  • 30 Sept 2016, 04:11 pm

Activity

Show:

Michael Offner 11 October 2016 at 17:19

Michael Offner 11 October 2016 at 16:41

better workaround:
download MSSQL extension from here
http://stable.lucee.org/download/?type=extensions
and install it.

Michael Offner 11 October 2016 at 16:14
Edited

workaround:
at the following function to the MSSQL.cfc

public function customParameterSyntax() { return {leadingdelimiter:';',delimiter:';',separator:'='}; }

and store again the datasource in the admin.

Michael Offner 11 October 2016 at 15:37

this is related tp the new possibility tp define the separator characters.

Harry Klein 7 October 2016 at 14:29
Edited

thanks for the workaround - I will try it in my config file.
I looks like the issue was introduced in the snapshot you mentioned.

Fixed

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 30 September 2016 at 16:11
Updated 11 October 2016 at 17:54
Resolved 11 October 2016 at 17:54