Issues then come down to scalability and performance... XML is perfectly acceptable for some instances... If the data can be represented in memory without a significant footprint, it's probably a good idea. However, I have a colleague working on porting a solution that does a similar method for storing data, and the process of reading/writing to disk has some overhead, and now the application is being updated, and ported to a rdbms.
Having a standard format that can be scalable (such as what firebird offers) can be far more effective in dealing with larger data sets, and better scalability to a stand-alone server. Also, using a factory structure/provider can offer more transparancy for future portability. Some projects start with a stand alone data structure, but upgrading into an enterprise, or web based environment then becomes increasingly difficult. Bill Seddon wrote: > If it's for single user purposes, why not use a dataset that built from > XML? ADO.NET supports persisting a dataset to XML. If you are unsure > of the schema you should use, create the tables and their respective > columns and save the dataset as XML. > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Michael J. Ryan > Sent: 25 May 2007 17:30 > To: Tomek Lorek > Cc: Mono List > Subject: Re: [Mono-list] Database in a file > > I know I'm late chiming in here, but would suggest sqlite or Firebird... > Not > sure what the embedded firebird db offers in the *nix world, as I've > only used > it in windows. > > Tomek Lorek wrote: >> Hi there, >> I'm working on a simple CD catalog application and I need to store >> somehow the information on the files and directories. Text file is not >> good enough because it will be quite big and searching the information >> is quite slow and not optimal I guess (you always have to process each >> line of file from start until end). The best would be to use a >> query-driven database but I'd like it to be stored in a file. Could >> you suggest any way to make it in Mono? The application has to be >> easily redistributable and this is why I decided not to use >> mysql/postgres. > -- Michael J. Ryan - tracker1(at)theroughnecks(dot)com - www.theroughnecks.net icq: 4935386 - AIM/AOL: azTracker1 - Y!: azTracker1 - MSN/Win: (email) ... Ferengi Rule of Acquisition #146: If possible sell neither the sizzle nor the steak, but the Elphasian wheat germ _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
