Ryan, Yes, I do need to read the entire file into the memory first as I have certain business validations to be performed on the data read from a file. After these validations, I can dump the data into database
Regards, Girish Jain
From: Ryan Heath <[EMAIL PROTECTED]> Reply-To: "Discussion of advanced .NET topics." <ADVANCED-DOTNET@DISCUSS.DEVELOP.COM> To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] New Type decision Criterias Date: Fri, 13 Jan 2006 08:22:09 +0100 Interesting... Do you really need to read all file information into memory before inserting it into the database? If not, you could implement your *collection class* as an enumerable, that is, it will actively read the file for one record/class/struct (whatever you want to call it). and there for using one and only one instance of a record/class/struct, making the discussing struct-or-class irrelevant... This approach will *kick-ass* in a performance perspective. // Ryan =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
=================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
