bdarnell/torndb — pull request #15 by miso-belica (2013-09-30 11:55:58+00:00)
Title: Don't close connection after OperationalError

It's not possible to recover when expected exception
(e.g. duplicated entry, ...) is raised. It's possible
to recover by calling `reconnect` every time in catch
block but that's very annoying.

This behavior is also inconsistent with `executemany`
methods that don't close connection on exception.

Can you merge this change and publish fixed version of `torndb` on PyPI?