On Sun, 2 Jun 2002 07:20:53 -0700, Avi Nahir <[EMAIL PROTECTED]> wrote:
Avi, I think the main point in the in-memory dataset, is the ability to send it across the wire. I can have a remote server, WebSerrvice or other type of server create a recordset and transfer it to a client over http (through the XML serialization). That client does not have to have access to my database (i.e. accross a firewall). But the client can have all the benifits of a record set (like binding to a control, sorting, etc.). That is where I see the main use or recordsets. One cool tool is the ability to create a dataset class based on a table. You can then share this class with the client, so you both have the same recordset class. Hope this helps, Noam >Thanks, Greg. > >I undestand this "in memory" issue. However, what I'm thinking is: You are >supposed to take the data from a 'big' (say, SQL Server) database, work on >it in memory using a Dataset, and then return the modifications. But what >if, instead, you take the data, store it in an Access (Jet) database, work >on it (using possibly ADO.Net Command objects or dataset) and then, at your >leisure, return the modifications to the big database? > >The basic thing that bugs me: Being "in memory" is not enough merit for a >technology! I must be missing something. What? What is the advantage of >using an in memory Dataset as opposed to the scenario above? > > > >On Sun, 2 Jun 2002 08:26:31 -0500, Greg Ward <[EMAIL PROTECTED]> wrote: > >>> Should I use a Dataset or a local MS-Access database? >>> >>> The basis for my question: The dataset is touted as an in-memory >database: >>> It has schema, data, relations, filtering, sorting, and persistence >>> (through XML serialization). So, if it is "like" a database, why not >>> use "the real thing"? >>> >>> What is the crux of the difference between a local database and a >dataset? >> >>Well the big difference is that the dataset exists only in memory. You >could >>think of it as similiar to a disconnected recordset. You fill the dataset >with >>the data, view and manipulate as necessary, then save the data back to the >>database. If you had no database then of course you'd have no data to fill >the >>dataset with nor would you have a place to store changes. >> >>Greg Ward >>************************************ >>www.VB-FAQ.com >>VB Developer's FAQ site >>************************************ > >You can read messages from the DOTNET archive, unsubscribe from DOTNET, or >subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
