The PetaPoco.Database base implements IDisposable, so why don't most examples have a 'using' statement?

Question

The PetaPoco.Database object implements IDisposable, but I rarely ever see code samples (including PetaPoco’s own site ) that include the using as statement as follows:

using (var db = new Database("MyConnectionString")) { // Do database stuff } 

More often than not, I just see:

 var db = new Database("MyConnectionString"); // Do database stuff // I never see .Dispose() called. 

How should PetaPoco.Database objects be transferred?

Answer 1

As a simple rule: if the class implements IDisposable, then go ahead and wrap it when used. In fact, they cannot use any unmanaged resources, but it will not hurt and can protect you from changes in the future.

Answer 2

PetaPoco's helper is here. Dispose is the same as calling CloseSharedConnection() . However, C # syntax only supports (...) using IDisposable . For example, IDBConnection , from memory, supports both Close and Dispose .

Basically, it comes down to choosing

Example 1

 using(var db = new PetaPoco()) { // some code } 

Example 2

 var db = new PetaPoco() try { // code } finally { db.CloseSharedConnection(); } 

Answer 3

It depends on what you are implementing. The database is a database connection, you do not want to delete the connection every time you execute the sql statement in the database, because the performance will be terrible.

If you are using a web solution, you usually use one database object for each query, but this query certainly executes several sql statements in different filters, global filters and several control methods, so you cannot use Using

Answer 4

GC calls Object.Finalize . IDisposable not called by GC, it must be called manually. GC has nothing to do with using and IDisposable

Answer 5

IDisposable tells GC what to do when it wants to get rid of object .
using asks the GC get rid of object when its scope ends.
using using with object , which is not IDisposable useless.