search

LinuxDoku / migratordotnet

Automatically exported from code.google.com/p/migratordotnet
0 stars 0 forks source link

TransformationProvider should implement IDispose #119

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
TransformationProvider will leak database connections if neither Commit()
nor Rollback() are called--which is entirely possible if the provider is
used solely by a loader/migrator to determine whether the schema is
up-to-date.  The simple fix is to have TransformationProvider implement
IDispose, and to dispose of the database connection at that point if it is
opened.

Original issue reported on code.google.com by benjamin...@gmail.com on 4 Jun 2009 at 9:15

GoogleCodeExporter commented 8 years ago 
I have attached a patch.

Original comment by benjamin...@gmail.com on 4 Jun 2009 at 9:24

Attachments:

GoogleCodeExporter commented 8 years ago 
I have run into this issue as well and can verify that this is an issue.  It is 
especially apparent when using the Sqlite managed provider which does not do a 
good job 
of cleaning up after itself.

Original comment by messorian@gmail.com on 22 Sep 2009 at 3:18

GoogleCodeExporter commented 8 years ago 
SVN 142
Applied patch.

Original comment by geoffl...@gmail.com on 25 Mar 2010 at 10:05