Cool Extension Methods for IDataReader Interface

re: Cool Extension Methods for IDataReader Interface

Assam — Wed, 04 Feb 2009 09:08:36 GMT

I don't think this much number of methods is required. By the help of generics we can achieve the task. See the example below:

public static T GetValue<T>(this IDataReader dr,string columnName) where T : IConvertible

{

T retValue;

object obj = dr.GetValue(dr.GetOrdinal(columnName));

if (obj != null)

retValue = (T)Convert.ChangeType(obj, typeof(T));

return retValue;

}

re: Cool Extension Methods for IDataReader Interface

eKnacks — Thu, 11 Dec 2008 04:51:57 GMT

You've been knacked. Keep up the good work.

re: Cool Extension Methods for IDataReader Interface

Damon Carr — Tue, 24 Jun 2008 07:35:43 GMT

The performance difference is irrelevant when compared to the total time. It is almost all out of process work.

Also, you will typically gain far more net net when you have code that might be slower (but noticably bad is the point) yet more readable.maintainable.

Unless you are building real-time systems, server based multi-threaded transaction servers, etc. the entire 'general focus' on performance optimizations should not exist more times then not.

Force yourself to optimize your code at the end of your iterations and see the large savings in time, reduction in often unnecessary code and overall bandwidth improvement,

Kind Regards,

Damon Wilder Carr

http://damon.agilefactor.com

Benchmarking do dataReader.GetOrdinal() « Programatik - O local do estagi??rio de Inform??tica

Mon, 12 May 2008 14:51:57 GMT

Pingback from Benchmarking do dataReader.GetOrdinal() « Programatik - O local do estagi??rio de Inform??tica

re: Cool Extension Methods for IDataReader Interface

raj — Fri, 02 May 2008 14:02:44 GMT

Hi Chris,

Thanks for your excellent feedback. I have updated my post to point users to your comments. Appreciated :-)

Cheers,
Raj

~~~ CODING FOR ETERNITY !!! ~~~

re: Cool Extension Methods for IDataReader Interface

Chris — Thu, 01 May 2008 14:32:04 GMT

"Because ordinal-based lookups are more efficient than named lookups, it is inefficient to call GetOrdinal within a loop. Save time by calling GetOrdinal once and assigning the results to an integer variable for use within the loop." msdn.microsoft.com/.../system.data.sqlclient.sqldatareader.getordinal.aspx

Cool Extension Methods for IDataReader Interface

DotNetKicks.com — Tue, 15 Apr 2008 22:55:09 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com