Bug #108335 Contribution: Fix executemany batch insert operations sentinel RE
Submitted: 30 Aug 2022 12:24 Modified: 13 Oct 2022 17:31
Reporter: OCA Admin (OCA) Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connector / Python Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any
Tags: Contribution

[30 Aug 2022 12:24] OCA Admin
Description:
This bug tracks a contribution by Alex Cazacu (Github user: acazacu) as described in http://github.com/mysql/mysql-connector-python/pull/81

How to repeat:
See description

Suggested fix:
See contribution code attached
[30 Aug 2022 12:24] OCA Admin
Contribution submitted via Github - Fix executemany batch insert operations sentinel RE 
(*) Contribution by Alex Cazacu (Github acazacu, mysql-connector-python/pull/81#issuecomment-1231391781): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: git_patch_1027665146.txt (text/plain), 868 bytes.

[1 Sep 2022 12:19] MySQL Verification Team
Hello,

Thank you for the report and contribution.

Regards,
Ashwini Patil
[16 Sep 2022 4:39] Alex Cazacu
Hi MySQL,

I can understand how this issue is non-critical, as the batch inserts are still functioning. However, they do so at a massive performance penalty.

Do you have a timeline for when this fix will be released into a new version of the connector?

Thank you!
[12 Oct 2022 15:57] Julian Briggs
Pls up the severity of this bug.
We routinely executemany with 30,000 rows
This bug means that instead of a sending a single multi-row query,
the connector sends 30,000 single rows queries. :-(
This has a devastating impact on performance: connection exhaustion, slow queries etc.
Until the bug is fixed we will run on 
Mysql Python connector 8.0.29
:-(
[13 Oct 2022 9:52] Alex Cazacu
Timeline of this issue:

1. I opened a bug in this platform.
2. I created a PR with the fix in the repository, and referenced it back here.
3. My PR was closed.
4. A new issue was created here with a diff of my fix.
5. ?

It baffles me that a change as trivial and impactful as this one has to go through so many procedural hops and gateways and still, two months after having first been reported, lie here untouched.
[13 Oct 2022 17:28] Oscar Pacheco
Posted by developer:
 
This bug is a duplicate of https://bugs.mysql.com/bug.php?id=108145. BUG#108145 (MySQLCursor.executemany() fails to correctly identify BULK data loading ops) is on its way to being fixed. 

Thanks for the contribution.