Devart Forums

This is a major issue. Current MySQL driver implementation DOES NOT account for this charset (utf8mb4), it is simply not supported. First, there is a constant limit of MaxChars in UTF set to 3. Second, the connection issues command 'SET NAMES utf8' that makes it impossible to use utf8mb4 -- there is an error when the 4-byte UTF symbols are inserted into the utf8mb4 database/table/column. I was able to manually enter utf8mb4 into the SET NAMES command in the source codes and fix some comparisons to include utf8mb4 charset in some of the MySQL units, which stopped this error. However, still, the high surrogates become corrupt (due to the fact that the internal functions do not support them when converting this from Delphi's UTF-16, generating garbage). Please fix ASAP - this IS a bug as it utf8mb4 is the only format that fully supports the entire UTF universe, and the simple UTF8 usage is NOT recommended for MySQL deployments.

1. Can you please explain the difference between the methods "Read" and "ReadNoWait" that are implemented in TCRSSLIOHandler / TMySSLIOHandler / TCRIOHandler .

2. On a separate note, both classes are not documented in the Help, but are required for SSL to work. It's a black box for the end users, not to mention there are dozen of posts here on this forum from people who can't event find the units for them. Please fix this in the next release of help.

Thank you.