The questions about saving files in a database is a reoccurring subject
of this mailing list.
How about adding a feature request for something like a
sqlite3_bind_file() to load a file into a statement and maybe a
sqlite3_column_savefile(). I guess this could solve some things like not
loading the whole file into memory and instead stream the file on commit.
Oracle has something similar like this in the PHP-implementation (
http://se2.php.net/manual/en/function.oci-lob-import.php )
Personally I think that files should be save like files on the filesystem.
Best regards
Daniel
Eduardo Morras wrote:
At 19:00 18/03/2007, you wrote:
Hello John,
thanks for the valuable piece of advice. The idea is that either
1) I store data in tabular form and work with them
2) I create a table of blobs and each blob is the binary content of a
file
(2) is my method in question, for (1) we all know it works. So I
turned to
SQLite just because it seems that it is a lighweight single file
database.
So, even if i don't like (2), I can setup an implementation where I
have a
file system inside a fully portable file.
BR
dimitris
You can use zlib to dwhat you want. It has functions for add and
delete files, it's flat file and provides medium/good compression. You
can store your file metadata on SQLite as zip filename, name of the
binary file, an abstract or even a password for zip file.
HTH
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
