Ann,

Le 08-févr.-05 à 18:02, Ann W. Harrison a écrit :

> Yup, except that I'd use 32K because I don't trust all the utilities to
> handle 64K right.

Good point. Thanks!

> There's no particular benefit to fitting segments on pages. A segment
> has minimal structure - just a two byte length - and the system will
> pack the segments regardless of page boundaries. If your first segment
> fills 14.4 pages, the next will start on the next free byte of the 15th
> page and continue from there.
> With records, the system won't write a new record on a partially filled
> page unless there's room for the whole record - or the record,
> compressed, is still larger than a page.
> Blobs are different. If you've ended one segment part way through a
> page, the next segment will follow it immediately, even if that segment
> won't fit completely on that page.
> Hope this helps,

Oh yes, thanks. That is perfectly clear, a very usefull answer.
And 32K is the way to go.
One could anyway wonder if the best is 32K - 1 bytes or exactly 32K
bytes... ?
I'd say 32K - 1 bytes might be safer if some utility still uses a
signed 16 bits integer somewhere for the size. But does this sound
possible that some utility would still use 16 bits signed integers for
these tasks?

--
Olivier Mascia