Bug #70493 | `compare' symbol in ODBC conflicts with XSB Prolog | ||
---|---|---|---|
Submitted: | 2 Oct 2013 20:50 | Modified: | 13 Feb 2023 21:40 |
Reporter: | Jess Balint | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 5.2 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[2 Oct 2013 20:50]
Jess Balint
[3 Oct 2013 10:35]
Bogdan Degtyariov
Thank you Jess. Indeed, that function has to be renamed into something less ambiguous.
[8 Feb 2023 3:07]
Bogdan Degtyariov
Posted by developer: The symbol collision was resolved by renaming `compare()` function to `parser_compare()` in the parser module of ODBC driver.
[8 Feb 2023 3:07]
Bogdan Degtyariov
Posted by developer: The symbol collision was resolved by renaming `compare()` function to `parser_compare()` in the parser module of ODBC driver.
[13 Feb 2023 21:40]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Connector/ODBC 8.0.33 release, and here's the proposed changelog entry from the documentation team: Renamed compare() to parser_compare() in the parser module to avoid a symbol collision with the XSB ODBC interface. Thank you for the bug report.