Re[2]: [sqlite] reg:blob data reading
Hello Dennis, Monday, September 18, 2006, 11:50:03 AM, you wrote: DJ> Jay Sprenkle wrote: >> On 9/18/06, Teg <[EMAIL PROTECTED]> wrote: >>> Hello Jay, DJ> Everyone has different needs. We like keeping all of the data (blobs DJ> included) in one data file. We also use the encryption extension, and DJ> it is mandatory that our blobs be encrypted. I don't need "read DJ> arbitrary byte ranges from a blob" for my work project, but I could use DJ> them in a personal project that involves sqlite (no encryption here; but DJ> it is important to keep all data in one data file). DJ> - DJ> To unsubscribe, send email to [EMAIL PROTECTED] DJ> - I'm, probably going to be offering optional encryption too. Why did you chose to use the SQLite encryption extensions versus just encrypting the blobs after you read them back in and before you write them out? -- Best regards, Tegmailto:[EMAIL PROTECTED] - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: Re[2]: [sqlite] reg:blob data reading
On 9/18/06, Teg <[EMAIL PROTECTED]> wrote: Hello Jay, The whole reason I store files in the DB in the first place is to have a single "package" to move around and backup when needed. My application is storing whole series of PNG and JPG files in the DB with meta data describing where the images came from. My technique won't help you then. I use it for things like scanning images of documents and using the database to keep track of the documents. I never have to search a picture using a select statement so it would be silly for me to put them into the database. I just back up the file system using off the shelf backup software and it works fine. -- SqliteImporter and SqliteReplicator: Command line utilities for Sqlite http://www.reddawn.net/~jsprenkl/Sqlite Cthulhu Bucks! http://www.cthulhubucks.com - To unsubscribe, send email to [EMAIL PROTECTED] -
Re[2]: [sqlite] reg:blob data reading
Hello Jay, Monday, September 18, 2006, 9:23:27 AM, you wrote: JS> On 9/18/06, sandhya <[EMAIL PROTECTED]> wrote: >> I think too, if they are Big-Blobs, it is better to store only a Reference >> to a File. >> >> May i know litlle more clearly about this?What it mean actually? JS> Store the path to the file in the database ( C:\somefile.dat or JS> /tmp/somefile.dat ). JS> Then open the file using regular file handing routines ( fopen() etc ). JS> - JS> To unsubscribe, send email to [EMAIL PROTECTED] JS> - The whole reason I store files in the DB in the first place is to have a single "package" to move around and backup when needed. My application is storing whole series of PNG and JPG files in the DB with meta data describing where the images came from. I like the concept of being able to set an upper limit on the number of retrieved bytes on a blob. I don't see any easy way to do it though. My images files tend to be from 50-500K so, performance wise it's pretty quick. -- Best regards, Tegmailto:[EMAIL PROTECTED] - To unsubscribe, send email to [EMAIL PROTECTED] -
