Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
.`pyodbc` works again with `MariaDB 10.3`
The `pyodbc` module did not work with the `MariaDB 10.3` server included in the RHEL 8.4 release. The root cause in the `mariadb-connector-odbc` package has been fixed, and `pyodbc` now works with `MariaDB 10.3` as expected.
Note that earlier versions of the `MariaDB 10.3` server and the `MariaDB 10.5` server were not affected by this problem.
Description of problem:
The combination of pyodbc-4.0.30, mariadb-server-10.3.27-3 and mariadb-connector-odbc-3.0.7-1 leads to the issue, which makes pyodbc unusable(exec method every time fails).
Every query attempt returns : pyodbc.DataError: ('22018', '[22018] [ma-3.0.7][10.3.27-MariaDB]Invalid character value for cast specification (0) (SQLExecDirectW)')
Version-Release number of selected component (if applicable):
How reproducible:
install mariadb-server-10.3.27-3, mariadb-connector-odbc, unixODBC, pyodbc
set up correctly drivers
run a simple query via pyodbc API
Reproducer available here [1]
[1] https://github.com/devexp-db/pyodbc-tests/tree/master/Sanity/mariadb-odbc
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (mariadb-connector-odbc bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:4163
Description of problem: The combination of pyodbc-4.0.30, mariadb-server-10.3.27-3 and mariadb-connector-odbc-3.0.7-1 leads to the issue, which makes pyodbc unusable(exec method every time fails). Every query attempt returns : pyodbc.DataError: ('22018', '[22018] [ma-3.0.7][10.3.27-MariaDB]Invalid character value for cast specification (0) (SQLExecDirectW)') Version-Release number of selected component (if applicable): How reproducible: install mariadb-server-10.3.27-3, mariadb-connector-odbc, unixODBC, pyodbc set up correctly drivers run a simple query via pyodbc API Reproducer available here [1] [1] https://github.com/devexp-db/pyodbc-tests/tree/master/Sanity/mariadb-odbc