On Wed, 12 Aug 2009 09:22:47 +0200 I. Szczesniak wrote:
> On 8/10/09, Glenn Fowler <[email protected]> wrote:
> > (although the ast code may convert runs of 0's in real data to holes)
> This conversion of 0's to holes is an actual problem for databases. A
> hole in a file may reflect 'no records here' for a database while 0's
> reflect that the record is valid and contains 0's as data.
does an application really have fine grain control over holes on the write side?
isn't there a minimum hole size?
e.g., does the following *always* create a file with a 1 byte hole at offset 1?
open for write
seek 0
write 1 byte
seek 2
write 1 byte
close
_______________________________________________
ast-developers mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-developers
