Subject: Re[6]: T5 database HotSync file size problem From: Adrien Regimbald <[EMAIL PROTECTED]> Date: Wed, 11 May 2005 13:27:51 -0600
I suppose my own development experience with the Palm has biased my opinion on how the platform is typically used. For example, I've never thought that features like unique IDs and record attributes were worth the bother of using them, and most of the Palm databases I work with use fixed length records for the main data. Where possible, I store string data in a separate database, in a more relational database fashion. We'd have to conduct a survey to determine whether the average Palm developer uses fixed length records or not, but either way, my assumption was probably unfounded.
Those of us who routinely deal with large databases understand that the HotSync download speed problem is not specific to the T5 but is generic to HotSync across all Palm OS units.
It is quite easy to build your own database packing system, and even easier if you use fixed length records, but if your application uses fixed length records then you are missing out on one of the advantages of a memory-based OS like Palm OS over disc-based OS like Windows. Specifically that variable length records and blocks are handled very efficiently by Palm OS.
Roger Stringer Marietta Systems, Inc. (www.rf-tp.com)
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
