I'd say it depends on the type of the variables that make up your 16 bytes.
Plus, logging 16 bytes every 2 secs for 24hrs is a allot more than 300K.
24hrs x 60min/hr x 30readings/min x 16bytes/reading = 675K.
You will also have some overhead associated with each DB and each record.
(using the data from my earlier DB record size post) Your DB may be as large
as: header + 43200 records = 84 + (43200 * (16 + 16(record overhead)) =
1.3MB or there about.
There is a limit on amount of data per record (its just under 64K), so
either you will have to save blocks of data readings to records (to reduce
the overhead) or save each data reading into an individual record (saves
programming time).
Depending on the data, if its a float, integer or string (or mix of each)
you may be able to compress your data and/or remove blank spaces. Anyway you
store it, it will be allot of data on your Palm.
The actual format of the data you wish to save will depend on the best
method to store it. If you wish to save on overhead bytes, you will need to
create a structure and functions to write your readings in blocks. If you
write each readings to individual records, you can use a simple structure
assignment to the DB chunk.
Hope it helps,
Dave
-----Original Message-----
From: Stuart Norton <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, June 29, 1999 11:07 AM
Subject: Database advice
Hi,
I'm developing an application to log data of 16 bytes every 2 seconds for a
whole day, and then upload/synch to a PC. This is a total of about 300K. Can
anyone advise me on the best Data structures/Database format to use. I'm new
to all this!
Thanks,
Stuart Norton,
University of Southampton, UK
