How can I store images into the database

briswei

Hope that You can help me, Thanks in advanced !!!
I hv managed to store html file with images as binary type "longblob" into database. Then , i can view the html files with images even after i have deleted the physical location of html file. For security purpose, i need to delete the physical location of html file & images. But , the problem is if the html files contain images, it will only show a broken image link with blank rectangular after i hv deleted the physical location of images files. How can I store the images that appears within HTML files into the database ?

I can't solve my problem by storing the image name/ location. Actually i'm storing the whole HTML file into database & I'm not sure how many images will be in that HTML file , & what are the images files name. I do not know in advanced the contents of the HTML file that I will store & what are the images that appear in the HTML file, It change based on user selection. Do u hv any idea to solve this problem ?

this is my code to add files into database:

$form_data = "C:\Program Files\Apache Group\Apache\htdocs\index.html";

$data = addslashes(fread(fopen($form_data, "rb"), filesize($form_data)));

$q = "INSERT INTO binary_data (bin_data) VALUES ('$data') ";

this is the code to retrive files from database:

set_magic_quotes_runtime(0);
$data = @MYSQL_RESULT($result,0,"bin_data");
$type = @MYSQL_RESULT($result,0,"filetype");
$data = stripslashes($data);
$data = stripslashes($data);
echo $data;

sahammondsr

This is going to be considerably more complex then the code sample you offered above.

One way of tackling it might be as follows:

Two separate MySQL tables, one for storing the html files themselves, another for storing the image.

Then, the script which retrieves the html file has to be made much more "aware" such that it can parse the HTML file and find references to images. It has to be smart enough to know the base URL or file location of each image reference based on relative paths (if they occur within the html document) as well as absolute references to images.

That program could then retrieve and store the image in the images table and return back the row id or unique name for the saved image. It could then replace each image reference with something like "<img src='/php-bin/display_image?id=999999'>".

You'd of course develop a separate ap called "display_image" and use it to simply do a MySQL query to retrieve the image and then send it out to the user.

There are perhaps other solutions. That's how I would tackle it. Obviously considerably more complex then your original example, however, much more largely scalable and applicable in other potential environments.

Scott A. Hammond, Sr.
http://www.primainternet.com

saltwater

Indeed, thats the way to do it I think

saltwater

oh, and to show the image's, I use an external script (my imgage tags look like this <img src="img.php?id=1>

and the basic of the external script (img.php) like this:

header ("Content-type: image/pjpeg"); // if you are using a jpeg image

$querydone=mysql_query("SELECT image FROM images WHERE id='$id'");
echo mysql_result($querydone,0,0); // just echo the binary data

saltwater

sorry guys, I put this reply in the wrong place 🙂

[deleted]

What exactly is the reason that you 'have' to store everything in the database?

Anon

i never understand why people do this either..... if you are going to create a new table, with just a unique image id, and the image bytes... why not just create a directory, and save the files as:

unique_id."_originalfilename.ext

for database sites that get hit like a f\/ck like mine, you aren't going to want to load the database with anymore images... unless of course you want to start another amicopyingsomeoneelseornot.com websites........

sahammondsr

Completely agreed.

I would never advise someone to simply store images within a database or html files for that matter, rather simply save them under unique names and alter the html file on the way in to reference the newly named/saved images.

Much less load on the server. Why in the world fire up PHP, connect to MySQL, execute a query, wait for the data to come back, and stream that out to the user, when the initial page generate could directly reference the images.

My advice above was only in direct reference to the defined objectives of the user (can't save the file, can't save the image). Definatley not something I'd agree is worth doing if I were simply asked how to store documents locally including images, etc.

Scott A. Hammond, Sr.
http://www.primainternet.com