[ODBC-222] Make SQLExecDirect to use text protocol(i.e. mysql_query) Created: 2019-02-12  Updated: 2023-04-13  Resolved: 2023-04-13

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: General
Affects Version/s: None
Fix Version/s: 3.2.0

Type: Task Priority: Major
Reporter: Lawrin Novitsky Assignee: Lawrin Novitsky
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to ODBC-220 ODBC Connector Prepares Statements on... Closed
relates to ODBC-286 Very Poor Performance on Remote Conne... Open

 Comments   
Comment by Lawrin Novitsky [ 2023-04-13 ]

The change have been pushed in few commits beginning with 66c21a2f65eb0466806090746acb58190f1ac716. SQLExecDirect now uses text protocol and client side prepared statements(CSPS). That can be switched to use of binary protocol and server side prepared statement(SSPS) if necessary(for example for CALL statement).
SQLPrepare uses by default SSPS, but it can be switched to CSPS, for example in case of multistatement query.
The option to also use CSPS by default in SQLPrepare has been added, its name is PREPONCLIENT. In some case it will be automatically switched to SSPS - one of cases of request of metadata before SQLExecute call.

Generated at Thu Feb 08 03:27:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.