On Wed, Jun 9, 2010 at 8:49 AM, Jean-Denis Muys <jdm...@kleegroup.com> wrote: > > On 6/9/10 14:37 , "Simon Slavin" <slav...@bigfraud.org> wrote: > >> >> On 9 Jun 2010, at 12:18pm, Navaneeth Sen B wrote: >> >>> I would like to know how i can store an AVCHD file(It has a folder >>> structure) having size greater than 4GB. >> >> It is unlikely that whatever filesystem you're using will allow any file to >> be >> this big. Therefore you cannot have a database file this big either. Leave >> the folder the way it is, and put the filenames into your database. >> > > Modern file systems allow files with sizes weighing in TB. HFS+ for example, > which we have been using for a number of years already, has a single file > size limit of 8 Exbibytes. >
Indeed. See http://support.apple.com/kb/HT2422 "The theoretical maximum file size for a Mac OS Extended file system is millions of terabytes. In practice, the maximum file size is equivalent to the maximum volume size, except for a small amount of disk space reserved for file system information." Even in version 10.0 of Mac OS X (about 8 or 9 years ago), the max file size was 2 TB. Re. OP's question, if the AVCHD "file" is really a folder, you would probably want to tar-gzip it into a file if you want to store it in a db. That said, it is probably not a good idea to store it in a db. Instead, store the metadata for the file in a db while keeping the file on the file system, and then use the metadata to locate the file. All of Jean-Denis' earlier reasons apply. The general rule of thumb -- if you have lots and lots of tiny binary files, store them in the db. This would be especially efficient if the size of each file is less than the page size in the db, so the files don't span pages. And, this would be especially useful if you don't want to come up with a naming and storing structure for lots and lots of such files. An example of the above might be thumbnails of photos (not actual, full size photos, but just the thumbnails), or 30 second samples of music, etc. The max page size allowed in sqlite is 32 K, so that is a good limit to impose. On the other hand, if you have a few very large files (or a lot of very large files) then it is better to store the metadata for those files in the db, but store the files in the file system. > Now your suggestion is sound, as I argued previously. > > Jean-Denis > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu ----------------------------------------------------------------------- Assertions are politics; backing up assertions with evidence is science ======================================================================= _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
