Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

Thanks. It's a shame there wasn't a test to catch this in the first place.

Can you think of a test for this? Maybe looking at the way inserts get generated?

If not, I will. :)

Hey @jimfulton, I would appreciate your help in adding tests.
unfortunately, I don't have enough time at the moment to dive into one more library. Good, that this problem can be easily monkey-patched.
Feel free to close the PR and submit changes under your account as well.
It will help me to avoid cla signing, etc.

OK. Created #226 to track.

@devbis this doesn't do what I guessed it did. :)

What motivated you to do this -- what breaks without it?

Reopening to see if any tests are affected.

@devbis this doesn't do what I guessed it did. :)

What motivated you to do this -- what breaks without it?

Sorry for the delay.
I'm trying to bulk insert with the following code:

session.execute(insert(model).values(list_of_dicts))

I want to make the following insert in SQL

INSERT INTO table VALUES (...), (...), .... (...);

It takes the same time as a single insertion, but I can uploads many items at once.

And without this feature enabled SQLalchemy doesn't allow to do it.

Thanks. Hm, that's what I thought too... I'll look some more.