What happened?
In this PR the base init function of ADBC driver changed from FlightSQLDriverInit to FlightSqlDriverInit and this causes failures in the application that uses the latest build of the driver.
Should we support both FlightSQLDriverInit and FlightSqlDriverInit in this case?
Stack Trace
No response
How can we reproduce the bug?
There is no function available with name FlightSQLDriverInit
Environment/Setup
No response