-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are PreProcessSQL() and PreProcessBindSQL() still needed? #437
Comments
This is fairly confusing. See perl5-dbi/DBD-mysql#106. According to https://metacpan.org/changes/distribution/DBD-mysql the old buggy version of DBD::mysql was restored in DBD::mysql 4.0.43. This means that the comment in Kernel/System/DB/mysql,pm is obsolete:
My preferred solution is to switch to DBD::MariaDB. See https://metacpan.org/pod/distribution/DBD-MariaDB/lib/DBD/MariaDB.pod#UNICODE-SUPPORT. One thing that should be done, is to require DBD::mysql 4.0.43+ for OTOBO. This would remove some failure modes. |
If DBD::mysql 4.0.43 is available for all supported Distros, this can be removed, and 4.0.43+ can be required. (DBD::mariadb should probably be used longterm.) |
DBD::mysql 4.043 was released more than five years ago. I suppose that this version is now available in the usual LTS Linux distributions. |
https://pkgs.org/search/?q=dbd-mysql https://repology.org/project/perl:dbd-mysql
|
Thanks to @daxim for looking that up. So instead of requiring DBD::mysql 4.043 or higher, I'd rather put DBD::mysql 4.042 on the blacklist. |
Because this is the primary use case.
as this was just a workaround for DBD::mysql 4.042, which is blacklisted now
DBD::mysql 4.042 is now on the blacklist. The SQL preprocessing has been removed. The test suite looks fine, and a quick sanity test looked fine too. Closing this issue. |
The methods are only defined only for
Kernel::System::DB::mysql
. The explicitly encode the strings sent via the MySQL database connection. My hunch is that this might no longer be necessary. Needs to be investigated.The text was updated successfully, but these errors were encountered: