> ... But what if I wrote a conduit for PC only but not for a
> Mac (or users just doesn't want to install the conduit). So, would
> there be any problem if we use DmDeleteRecord to delete a record but
> user rely only on the backup conduit? Would the database header get
> saturated with deleted record info and not allow any new record to be
> created? ...
Interesting question. :)
The deleted records take some space, and consume a "record number". Neither
is likely to be a serious problem in practice, but it really depends on how
the user works. If he creates and deletes a lot of records (high turn-over),
he could run out of record numbers. Without a conduit, it'd take a lot of
Graffiti strokes to do this!
I don't know the exact amount of memory to store a deleted record -- let's
say it's 8 bytes. So a database "full" of deleted records would consume 64K
* 8B = 512KB. That's a lot of memory to waste, but it's a small fraction of
the space available on a typical 8MB device.
You could provide a Purge command to clear out all deleted records. This is
different than the Purge commands in Datebook and To Do, so it'll require
explanation. A more automatic solution would be to clear out deleted records
automatically if you detect that you're running without a conduit. Look at
it this way: you don't really need to keep deleted records around until
after the user first HotSyncs with your conduit. Until then, none of the
records are known outside the device, so it's safe to remove them.
--
Danny @ Palm
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
