On Wed, Nov 6, 2013 at 1:54 PM, Petite Abeille <[email protected]>wrote:
> > On Nov 6, 2013, at 7:42 PM, Ulrich Goebel <[email protected]> wrote: > > > Every hint is welcome! > > Don't store your files in the database. Store them on the file system, as > the Almighty intended. Much simpler and flexible altogether. > > Perhaps of interest: > http://www.sqlite.org/intern-v-extern-blob.html > I'll argue to the contrary. In many situations, it is appropriate and preferable to store images or other content files in the database. That keeps all the content associated with an application together in a single place. And it allows content updates to be atomic. If you are using something like the SQLite Encryption Extension, it also encrypts your content automatically. The Fossil DVCS system is an example of this: All content files are stored in a single SQLite database. Monotone is another DVCS (the original DVCS, as far as I am aware) which does the same thing. See http://www.sqlite.org/whentouse.html#appfileformat for further thoughts on this. SQLite is commonly used as an application file format. In such cases, it is entirely appropriate to store content files directly in the database, rather than as separate files on disk. -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
