search

nemequ / sqlheavy

Automatically exported from code.google.com/p/sqlheavy
Other
5 stars 4 forks source link

Separate connection code from Database class #4

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Creating a separate Connection class would allow us to transparently support 
multiple connections to the same database. This could allow us to avoid 
blocking when starting a transaction while another transaction is still 
outstanding.

Two problems with this idea are that temporary tables do not persist across 
connections (therefore this would have to be an optional feature, likely 
disabled by default), and nested transactions wouldn't be able to work (and, 
therefore, should continue blocking).

Original issue reported on code.google.com by nem...@gmail.com on 8 Jun 2011 at 8:26