Hey:
>
>
> File size probably shouldn't be a problem. Currently running under Linux
> which supports 4G (maybe more?) files. I'm pretty sure BerkeleyDB will
> handle files to that size since MySQL uses it on the back-end for it's
> InnoDB tables (I *think*).
No. MySQL has two (actually three, one appears to have died on the vine.) table
handlers that are transaction safe:
BDB and InnoDB.
The BDB implementation was developed by the MySQL folks I think.
InnoDB is a separate thing developed by a separate company.
http://www.innoDB.com/ They have become more closely integrated with MySQL as
of release 4.0.x however. InnoDB is tablespace based. Multiple tables per
space and multiple files per space. They are not as slick as some commercial
DB tablespaces, but they are getting better with every release.
> At any rate I know we have DB files in excess
> of 1G so I'm not too concerned about that.
As I said InnoDB tables support using multiple files per tablespace. Or what
ever they call them in MySQL. I forget.
I think InnoDB also supports auto extend in some form in release 4.0.2.
Anyway, large files can cause other interesting complications like: How well
does your backup system handle them, if at all.?
Anyway filesize is worth keeping an eye on.
gat
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 15 20:33:35 2002