Fixing multi method for to_sql for non-oracle databases
- [ ] closes #57310
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/v2.2.1.rst` file if fixing a bug or adding a new feature.

Totally fair not to accept dialect specific changes, but with the previous commit, ALL queries using the method="multi" argument resolve to insertion via single row. Is it worth breaking this functionality just for the sake of the Oracle connector? I think it's reasonable to revert https://github.com/pandas-dev/pandas/pull/51648 that broke this for all `method="multi" ` queries. Would you be interested in making a PR to do that? Yes, I definitely can make that PR, should I keep it in this PR and just change it or make a new one?
Also, is it worth making a warning at least for Oracle? > Yes, I definitely can make that PR, should I keep it in this PR and just change it or make a new one?

Sure you can revert the code change in this PR. It would be good to add a unit test as well so it doesn't break again (`test_sql.py`)

>  Also, is it worth making a warning at least for Oracle?

Yeah in the docstring of `to_sql` that would be great Looking good but please run the pre-commit checks to fix style issues: https://pandas.pydata.org/docs/dev/development/contributing_codebase.html#pre-commit Thanks @kassett 