ENH #6416 improve performance on SQL insert
This empirically significantly improves write performance by allowing SQLAlchemy to use the `executemany` method of the driver if available.

@mangecoeur You have again a problem with the commits (messed up history) .. :-(

A first advice: don't work on master, but create a feature branch for every PR, eg in this case:

```
git checkout -b sql-perf
```

Secondly (but you should do this first, otherwise the history of the branch will also be messed up), to clean-up your history, maybe you can do the following (not fully sure this will work, otherwise @jreback can maybe give some advice):
- save your changes to somewhere else, for example another branch: `git checkout -b sql-temp`
- go back to master: `git checkout master`
- remove all your latest commits you see here in the PR, eg `git reset --hard HEAD~20` for going 20 commits back
- fetch latest upstream: `git fetch upstream`
- rebase your master to upstream: `git rebase upstream/master`
- Now create a feature branch: `git checkout -b sql-perf`
- Now you can try to cherry pick you latest changes (saved in the branch sql-temp) to your new cleaned feature branch: `git cherry-pick <commit>` (with <commit> being the hash of the particular commit you want to restore).
- then you can push this branch to github: `git push origin sql-perf` and create a PR with that.
 @jorisvandenbossche yeah i just realized my history is a mess. Am in process of dumping my repo and starting fresh from upstream master.
 If you follow my steps above, normally you should be able to easily recover your new commits and cleaning up the history without dumping your whole repo.

But in every case, when you have a fresh repo, don't work on master
 I know i shouldn't, was just in too much of a rush to git properly :P anyway, ended up nuking my entire fork and starting again, life is too short for merge conflicts! new PR: https://github.com/pydata/pandas/pull/6420
 Looks much better!

There seem to be some more commits in the above list that are not yet in pandas itself?

Closing this PR then.
 I think a lot of those commits got squashed when the main SQLalchemy work get merged. That merge history got mangled anyway since it was a bit of a mess, a lot of conflicts that i think jreback took care of.

On 20 Feb 2014, at 14:29, Joris Van den Bossche notifications@github.com wrote:

> Looks much better!
> 
> There seem to be some more commits in the above list that are not yet in pandas itself?
> 
> —
> Reply to this email directly or view it on GitHub.
 @mangecoeur Not yet the latest two I think: 'Added interval type' and 'Minor name change'.
 @jorisvandenbossche good point, they are actually included in #6420 now. Tests for timeinterval needed. the name changed will probably get overridden by the API design later on anyway.
