[#ODBC-89] Array insert performance is same as non-array insert connecting to Aurora database

[ODBC-89] Array insert performance is same as non-array insert connecting to Aurora database Created: 2017-03-15 Updated: 2021-03-04 Resolved: 2017-03-20
Status:	Closed
Project:	MariaDB Connector/ODBC
Component/s:	None
Affects Version/s:	2.0.13
Fix Version/s:	None

Type:

Task

Priority:

Major

Reporter:

Rahul Dhuvad

Assignee:

Lawrin Novitsky

Resolution:

Duplicate

Votes:

Labels:

None

Environment:

Linux64 & Windows64

Issue Links:

Duplicate
duplicates	~~ODBC-86~~	Optimize Array Insert	Closed

Description

MariaDB ODBC driver/connector accepts array insert (SQL_ATTR_PARAMSET_SIZE) via an ODBC application. However, when we tested, it turns out that it actually sends data row by row to the connected Aurora (or MySQL) database. Due to this, we are hardly able to see any performance improvement using array insert compare to non-array (row-by-row) insert.

Apparently we are seeing same behavior with latest MySQL ODBC driver/connector as well (v5.3.7) and we've raised similar bug against them as well (Bug #85266).

Comments

Comment by Rahul Dhuvad [ 2017-03-20 ]

This is duplicate of ~~ODBC-86~~; we can close this new one – I don't seem to have permission to close it myself.

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

[ODBC-89] Array insert performance is same as non-array insert connecting to Aurora database Created: 2017-03-15 Updated: 2021-03-04 Resolved: 2017-03-20