How do PIM's handle data?
Since someone mentionned PIM's again the other day, that got me wondering how those tools (Ecco, Notes, etc.) manage this kind of free-form data efficiently like notes or outlines, since I assume they don't store them in neat rows and columns?
Treepad's format is open and plaintext. Just go to www.treepad.com and browse around. It resembles XML.
What's wrong with storing them in rows and columns? Data is data, and most SQL DBMS manufacturers (I know Sybase ASA makes up most of the market) make embedded products which work on Palm-type products. Why reinvent the wheel?
Right, but I was wondering how you can make efficient random access if the data don't fit rows and columns, eg. one big note with no predetermined size?
Define efficient :) The quick little note app I just whipped up for myself just has all data in a table with one big text field. The search works by just using LIKE.
You could always define an overflow table, where the remainder of text for large entries can go. Then reference a row in there from the original.
H. Lally Singh
Not sure where Chandler is on how they are storing data now, but it is similar to Agenda. I think thery are using RDF as the model and maybe RDF/XML (Yuck!) as storage.
fool for python
Thanks everyone for the input :-) What I was curious about, is how to maintain good performance even though all data is saved in a single file, and data are pretty much free-form.
How do messages boards and Wiki's store text? How is a Wiki different from a PIM?
Precisely, do they just define a big, variable text column, and let the DBMS handle the issue?
I don't know, why not download one and find out?
Fog Creek Home