Convert_to_null Datasource

JayStan · September 28, 2020, 2:59pm

When updating a data source I need to change the page code from Convert_to_null to converttonull for the update to work. To do this I go into the browser debug and change the element. Is there a way to fix this permanently? Could you point me to the lucee code file this is located in so I can fix it?

Thanks

OS = Linux
DB = MySQL

System Information

||Version|Lucee 5.3.6.61|
|Version Name|Gelert|
|Release date|May 18, 2020||

Zac_Spitzer · September 28, 2020, 4:02pm

github.com

lucee/extension-jdbc-mysql/blob/master/MySQL.cfc#L18


			"If 'Use Unicode' is set to true, what character encoding should the driver use when dealing with strings?"),
		
		field("Alias Handling","useOldAliasMetadataBehavior","true,false",false,
			"Should the driver use the legacy behavior for ""AS"" clauses on columns and tables, 
		and only return aliases (if any) rather than the original column/table name? In 5.0.x, the default value was true."
			,"radio"),
		field('Allow multiple Queries','allowMultiQueries','true,false',false,
			'Allow the use of ";" to delimit multiple queries during one statement'
			,"radio"),
		
		field('Zero DateTime behavior','zeroDateTimeBehavior','EXCEPTION,ROUND,CONVERT_TO_NULL',false,
			'What should happen when the driver encounters DATETIME values that are composed entirely of zeroes (used by MySQL to represent invalid dates)? Valid values are "exception", "round" and "convert_to_null"'
			,"radio"),
		
		field('Auto reconnect','autoReconnect','true,false',false,
			'Should the driver try to re-establish stale and/or dead connections? If enabled the driver will throw an exception for a queries issued on a stale or dead connection, which belong to the current transaction, but will attempt reconnect before the next query issued on the connection in a new transaction. The use of this feature is not recommended, because it has side effects related to session state and data consistency when applications do not handle SQLExceptions properly, and is only designed to be used when you are unable to configure your application to handle SQLExceptions resulting from dead and stale connections properly. Alternatively, investigate setting the MySQL server variable "wait_timeout" to some high value rather than the default of 8 hours.',
			"radio"),
		field('SSL','useSSL','true,false',false,
			'Use SSL for connectiong the database.'
			,"radio"),
		field('Verify Server Certificate','verifyServerCertificate','true,false',false,

Please file a bug https://luceeserver.atlassian.net/ and a PR request against the
following file, include the bug number in the PR title.

Is this a just a bug, or will it cause backwards compatibility issues?

Can you include a link to the relevant mysql documentation about this change

Zac_Spitzer · September 28, 2020, 4:40pm

but the latest Lucee mysql driver already should support both?

this change was made in 8.0.13 and latest lucee driver is 8.0.19
https://bugs.mysql.com/bug.php?id=91421

JayStan · September 28, 2020, 9:46pm

I don’t think it even gets to mysql. I bet it is comparing the input name to some error checking field name. it errors off right away.

Zac_Spitzer · September 28, 2020, 10:29pm

can you post the actual error?