At 12:55 PM 10/31/2002 -0500, David Blocker wrote:
I BELIEVE that a row in a table has 10 bytes standard overhead, plus the number of bytes per column per row. So a table with 11 integer columns would have 10 + (4 x 11) = 54 bytes per row (4 bytes per integer colulmn)A table that with the same data takes 10 rows, with 3 columns would need: 10 x (10 + (3 x 4)) = 10 x 34 = 340 bytes PLEASE, Razzak, correct me if I'm wrong, but in terms of space it looks like a no brainer to use the first structure.
David,
Very correct!
You should also remember that the data in file2 is stored slightly differently since
the release of R:BASE 4.5. Now, each table will take up at least 8K (8192 bytes) of
disk space regardless of the number of rows. Even if a table has just one row, it will
require 8K of disk space. Each table's rows are now stored in 8K blocks rather than
just individual rows. This means that there are always 8K of contiguous rows of data
for faster retrieval. Because space for rows of data has been pre-allocated, you may
not see the size of file2 change as you add rows. The size of file2 will change only
when R:BASE needs to add a new 8K block for a table.
Hope that helps!
Very Best Regards,
Razzak.
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/
