>
> Turns out I was looking at the wrong function. Of course the database
> header will expand to multiple chunks if it can't grow the unique one.
>
> In practice, this almost never happens. Especially with big memory
> devices, it's almost always possible to resize a chunk up to the 64K limit.
> So only DBs with >8100 records (or DB's on very nearly full devices) will
> have multiple database header chunks.
>
> So this case might be exposing a performance problem with DB headers that
> have multiple chunks.
>
> The code to insert an entry into the middle of the list could be a lot
> better. Would you happen to be using a conduit that tries to do that?
> Normally new records are just appended to the end, and that should perform
> fairly well, even if there are multiple DB header chunks.
Uh, Bob, there's no way to add to add a record to anything *but* the end.
Even if you modify a record, it'll get deleted from its current position,
and then re-inserted at the end.
Actually, it's worse than that. When you write or modify a record, you're
not guaranteed *anything* about where it'll be inserted, although all
current devices install at the end.
>
>
> --Bob
>
> ________________________________________________________________________
> Bob Ebert, Consulting Engineer, Palm Computing Europe V: +33 4 9952.4354
> 77 rue Samuel Morse, 34935 Montpellier Cedex 9 France F: +33 4 9952.4397
>
>
--
Neil Rhodes
Calliope Enterprises, Inc.
1328 Clock Avenue
Redlands, CA 92374
(909) 793-5995 [EMAIL PROTECTED] fax: (909) 793-2545
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
