Hi, I really doubt that what audimanualspro says is correct. But I'd wait for his explanations.
As for why have separate MariaDB driver. They licensed differently - LGPL(MariaDB's) vs GPL(MySQL's). So forking was not really an option. And we need to support MariaDB server features that MySQL server does not have and MySQL driver won't support Best regards, Lawrin ________________________________ From: Volker Wysk via discuss <[email protected]> Sent: Thursday, July 3, 2025 6:19 PM To: [email protected] <[email protected]> Subject: [MariaDB discuss] Re: ODBC driver and SQLDescribeParam() Hi. Thanks for the reply. Am Donnerstag, dem 03.07.2025 um 03:23 +0000 schrieb audimanualspro--- via discuss: > This is a known limitation with the MariaDB ODBC driver — it doesn’t fully > support SQLDescribeParam() and defaults to SQL_VARCHAR. Unfortunately, > even in newer versions like 3.2.5, this behavior persists. > You might need to work around it by inferring parameter types manually That's not an option (if I get you right). > or switching to a driver with better metadata support like MySQL’s ODBC > driver. So the MySQL ODBC driver also works with MariaDB and and has metadata support? Then, why is there a distinct MariaDB driver, when the MySQL driver can be used? The MYSQL driver could be forked to get a working MariaDB driver. It's free software, after all... > https://audimanualspro.com/product/audi-a4/ That's product info about a car by the manufacturer Audi. Wrong link? Cheers, Volker _______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
