-
Notifications
You must be signed in to change notification settings - Fork 564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MySQL MariaDB ODBC memory allocation error on huge execute #721
Comments
Are you saying that after you execute 5000 huge upserts you get the error (suggesting a memory leak), or are you saying that a huge upsert of more than 5000 rows produces the error the first time you try it? |
@gordthompson After more than 5000 rows are being upsert with 1000 each round so sixth time (> 5000), or somewhere around there. I even tweak to use 1200 so after the fifth time (> 4800) it also breaks. The total data that is around 6500 rows. After I try this, even the normal slow |
It seems like this may be a bug in the ODBC driver. |
But it used to work though? So maybe I should try the MySQL own ODBC driver? |
You could perhaps try taking pyodbc out of the picture by running your SQL queries through the isql utility. See if you still get a memory allocation error. |
@keitherskine There is no issue when using it with isql directly with all the batches of data, of course I converted it to string without the |
Oh, looks like not using the |
Closed due to inactivity. Feel free to re-open with current information if necessary. |
Please first make sure you have looked at:
Environment
To diagnose, we usually need to know the following, including version numbers. On Windows, be
sure to specify 32-bit Python or 64-bit:
Issue
Often it is easiest to describe your issue as "expected behavior" and "observed behavior".
When
execute
in bulk (generating our own bulk upsert statement), after more than 5000 batches being executed consequently, it shows:executemany
does not have this issue but is very, very, very, very slow compared to this method.The text was updated successfully, but these errors were encountered: