Am Freitag, den 12.06.2009, 11:54 +0200 schrieb Sebastian Pipping: > Richard Hughes wrote: > > I'm slightly worried about it being called a service. Is it going to > > be a new process that just does the mapping or is this a bad choice of > > words? If it is a new process then I'm not sure such a thing will > > catch on. > > I'm not yet sure about how a mapper will keep it's data > fresh as the use of it is dependent on that. > Ignore my "service" for now. > > > > I'm also worried that a package manager has to read in and parse > > thousands of small files. > > While you mention "package manager" - with the current concept > the data will not be precise enough for use with a package manager. > > > > Why did you decide to write each project as > > a single xml file? > > - The other 99% of the database stay valid XML if a single > file is invalid > > - To better fit the version controlled environment > > > > Parsing and reading 10,000 files (in multiple directories) might take > > a few seconds, and would have to be copied into memory (few Mb) to > > query quickly. > > Correct. > > > > Which has to be invalidated if any of the files or > > directories change. Why didn't you just put them in a sqlite database > > that can be queried in a few ms, without dragging in an xml parser? > > Also 10,000 files take up way more space (and takes longer to install > > and update) than a single database file. > > I like your idea about sqlite. Maybe keeping the data to edit XML > and query and sqlite export snapshot is something to try. Why not use a XML database like dbxml? Maybe you could just specify the XML files as storage and then dbxml would do the rest.
> > > > XML might be > > useful for storing the data, but not for querying. > > Good point. Using XPath and XQuery you can do queries on XML as well. Cheers, Tiziano -- Tiziano Müller Gentoo Linux Developer, Council Member Areas of responsibility: Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor E-Mail : dev-z...@gentoo.org GnuPG FP : F327 283A E769 2E36 18D5 4DE2 1B05 6A63 AE9C 1E30
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
smime.p7s
Description: S/MIME cryptographic signature
