Hi On Tue, 19 Aug 2003 20:50:15 -0700, "Jeff Ishaq" <[EMAIL PROTECTED]> wrote:
>I would be interested to hear comments from other developers who have, >or are considering, building rather than buying a similar RDBMS system. At my company we have done similar work; however instead of storing the unique id as a reference to a record in another database, we always rely on the DmFindSortPosition method. Apart from that, we do manage a big collection of data spread across something like 10 related Palm databases that are sometimes fairly big. I wonder which is faster: - searching by record index: that is a linear search, but you only examine the record headers - searching by DmFindSortPosition: I believe that is a dichotomic search, but you get the overhead of getting, locking, unlocking the records. Did you make any performance measurements on this? How big are your databases? Another problem that we had to solve was: suppose you have a list of patients sorted alphabetically on their last name; at one point in the app you need to sort it by, say, test creation date. Option 1: sort the database on test creation date; this requires sorting everytime you change views. Option 2: maintain a database on the side, let's call it an "index database": this database has records that contain the test creation date and the patient record id (or some other method for uniquely identifying the patient) and is sorted on test creation date. When you display the list sorted by creation date, for every record displayed, you go get the patient in the database. We have been using option 2. This means creating as many index databases on the side, as there are fields that you are going to need to sort by. I suppose people who sell DBMS's for Palm must have done that kind of thing too as I dont see many other ways. Olivier Lancelot -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
