On 13/02/2012 2:18 AM, Thomas Mueller wrote:
Excellent! So what are the downsides of storing large files in the
database?
Originally, this was about loading the BLOB in memory, but now you
wrote about storing the BLOB in the database... H2 does store the BLOB
in the database file, which means less files, but the disadvantage is
that disk space is not returned to the file system immediately if you
delete many BLOBs.
When is the diskspace reclaimed?
For every byte you'd store, it would use 3x more
disk and memory resources. Is that still the case?
No, it never was like this. Why do you think so?
Some code repositories (I believe Mercurial) have this overhead. I
remember reading something similar about MySQL.
Thanks,
Gili
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
