I think when he asked about an IMDB what he really wanted was an in-proc db, from the description of the solution he was looking for. Jet is an in-proc file based db, and as far as I know its not ANSI SQL compliant, but it does work and is free. MSDE is a server based(runs in a separate process) ANSI SQL compliant db that is also "free". Any in memory datastore is usually not much use except as some sort of cache, unless you persist it to non-volatile storage at some point.
Writing your own persistence mechanism for an in memory datastore can be done, but why, when Jet and SQL Server/MSDE provide in memory adaptive caching that will probably run circles around anything you come up with and changes will be persisted immediately to NV storage? I've been down this road before, and the XML DOM is great for small amounts of hierarchical data, but as a full fledged db solution the XML DOM is not the right solution (yet). I am still hoping for someone to write a fast in-proc OODB(or even relational) in Dotnet to bridge the gap between XMLDOM/Datasets and MSDE. Perhaps something like www.db4o.com for Dotnet. Justin Harrell Vice President Development Aciss Systems Inc. -----Original Message----- From: Bill Schmidt [mailto:[EMAIL PROTECTED]] Sent: Friday, June 07, 2002 10:31 AM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Using DataSets as an IMDB However, none of the alternatives discussed so far are in-memory solutions. MSDE may be a relevant solution, but it requires an external (Access or SQL Server) database, doesn't it? Returning to the original poster's question, is it possible to do queries against the contents of a Dataset? If so, how? If not, this would obviously be a useful addition for v 2.0. Bill 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.
