Search:  
NamespacesDiscussions.NET v1.1Feedback
What data structure/objects to usde
Messages   Related Types
This message was discovered on ASPFriends.com 'aspngarchitecture' list.


Bill Bassler
The problem:
I have a VB 6.0/ASP app that I'd like to convert to .Net.
The app essentially pulls and combines event data from several sources.
The resulting data is sortable by time order and can be filtered by date and
or time.
Currently it uses a database table and SQL to collect, sort and filter the
events. When a run is complete, the table is disposed of.

The goal:
Ideally, I would like to do away the use of a database table as an
intermediate store to process the events. I've had to write a decent amount
of code just to attempt to clean the table up in the event of an error.
Database or otherwise. Also, SQL(#) temp tables will not work as this is a
web app with many short duration connections.

Ideas?
I was wondering if I could use something like an in memory XML DOM to store,
sort and filter event info... or is there a better choice to replace the
database table? Is there another .Net data object that is well suited to
this purpose?

The question
1 .Does this make sense.
2. Can I keep this object(s) completely in memory. To me, using an XML file
defeats the purpose.
3. Can I easily get the fine-grained time filtering and time sorting
functionality of SQL statements using (I guess XSL to HTML) conversion.
4. How robust will this approach be.
5. Anyone have a better idea.
Reply to this message...
 
    
=?ISO-8859-15?B?Sm/jbyBQYXVsbyBDYXJyZWlybw==?=
Hello Bill,

By your description (combine data in memory from several sources and
then sort it) the DataSet object is the ideal object.

You can think of it as as "mini" in memory DB.

--
Best regards,
João

Thursday, June 13, 2002, 6:10:22 PM, you wrote:

BB> The problem:
BB> I have a VB 6.0/ASP app that I'd like to convert to .Net.
BB> The app essentially pulls and combines event data from several sources.
BB> The resulting data is sortable by time order and can be filtered by date and
BB> or time.
BB> Currently it uses a database table and SQL to collect, sort and filter the
BB> events. When a run is complete, the table is disposed of.

BB> The goal:
BB> Ideally, I would like to do away the use of a database table as an
BB> intermediate store to process the events. I've had to write a decent amount
BB> of code just to attempt to clean the table up in the event of an error.
BB> Database or otherwise. Also, SQL(#) temp tables will not work as this is a
BB> web app with many short duration connections.

BB> Ideas?
BB> I was wondering if I could use something like an in memory XML DOM to store,
BB> sort and filter event info... or is there a better choice to replace the
BB> database table? Is there another .Net data object that is well suited to
BB> this purpose?

BB> The question
BB> 1 .Does this make sense.
BB> 2. Can I keep this object(s) completely in memory. To me, using an XML file
BB> defeats the purpose.
BB> 3. Can I easily get the fine-grained time filtering and time sorting
BB> functionality of SQL statements using (I guess XSL to HTML) conversion.
BB> 4. How robust will this approach be.
BB> 5. Anyone have a better idea.

BB> | [aspngarchitecture] member Click here to reveal e-mail address = YOUR ID
BB> | http://www.asplists.com/asplists/aspngarchitecture.asp = JOIN/QUIT
BB> | http://www.asplists.com/search = SEARCH Archives
Reply to this message...
 
 
System.Data.DataSet
Ad
MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT
 
 Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com