On 27 Aug 2001, at 13:37, Peter Epstein wrote:
> ...
>
> You might not want to do this if you have multiple references to the
> same string. In that case, I recommend creating references to database
> records based on the unique ID of the record. At one time, unique IDs
> weren't preserved after a hard reset and restore via HotSync, but that
> was a long time ago. Modern versions of Palm desktop and HotSync
> software for both Mac and PC preserve the unique IDs of records.
> Finding a record by unique ID is easy to do in code, but requires a
> linear scan of the records, which can be prohibitively slow. Sometimes
> a cache of the record index is useful to improve performance. -- Peter
> Epstein
>
May I ask which version of Mac HotSync manager that finally fixed
the bug of not preserving the unique ID?
One more piece of warning if people are thinking about using
record's unique id. With new devices such as m500, m505,
Handera, etc, people will start backuping databases on their SD
cards. I don't think there are any guarantee that the unique IDs will
be preserved when databases are copied over to those external
storage cards. The same is true for people trying to beam a
database to another device using third party software.
Also, correct me if I'm wrong, but I don't think there is any official
document (or I should say requirement) from Palm telling software
developer that they have to preserve unique IDs if a database is
beamed or copied to another device or storage cards. So if you
rely on the unique IDs, make sure you think about these special
cases.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
