RE: [plum] File uploads

[Philip Arnold]

Title: Message

This might be off topic for the question, but to save using BLOBs and the inherrant issues with strange characters, I tend to store the files in Base64 format, it makes the field a LOT larger, but it gets around any possible corruption issues.   Just use toBase64() to convert the file into the "text" format, then when you're ready to re-present it, use toBinary().   This seems to work for me - although people will probably complain about the storage overhead, but I look at it this way: hard disk space is CHEAP, so why not use it and save some stress and worry over possible file corruptions?   Cheers, Phil   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of K & N Parker Sent: 20 April 2006 22:26 To: plum@mail.productivityenhancement.com Subject: RE: [plum] File uploads Thanks Phil - traditionally I store the file on the server and store a reference to its file name in the database - what I am trying to achieve with Plum is what I usually do with Code Charge i.e. build a form that allows the user to point to the file on their local machine and when they hit the submit button it uploads the file to a specified directory and pops its file name into the record. I then use an application variable to build the URL to the file so that the application is always portable. I've always been interested in storing the file in the database as this protects it from prying eyes as I usually build sites in shared environments where the right type of security is not always easy to build. In respect to BLOBs I have yet to get my head around how to exactly do this in CFML.     ++++++++++ Kevin Parker Advanced Imaging (Aust) Pty Ltd   e: [EMAIL PROTECTED] w: www.advacedimaging.com.au   p: 08 8523 0225 f: 08 8523 0225 m: 0418 815 527 +++++++++