I am using the MySQL ODBC 5.2w Driver (5.2.3) and it appears that it does not follow the
rules for SQLConfigDataSource. The specification for the SQLConfigDataSource function
says that the attributes should be separated using a null byte and the list of attributes
terminated with a 2 null byte sequence, however the MySQL ODBC driver only uses the
supplied attributes if they are separated using semi-colons. This doesn't seem right.
Does anyone know when this was broken, or if there is any intention of fixing it?
Thanks for your input.
This message and any attachments are solely for the use of intended recipients. The
information contained herein may include trade secrets, protected health or personal
information, privileged or otherwise confidential information. Unauthorized review,
forwarding, printing, copying, distributing, or using such information is strictly
prohibited and may be unlawful. If you are not an intended recipient, you are hereby
notified that you received this email in error, and that any review, dissemination,
distribution or copying of this email and any attachment is strictly prohibited. If you
have received this email in error, please contact the sender and delete the message and
any attachment from your system. Thank you for your cooperation
|• Programmatic creation of ODBC DSN using SQLConfigDataSource||Nigel Meachen||2 May 2013|