thisnew — Thu, 17 Mar 2005 11:52:06 +0000

Two ways of dealing with that are to store the files on the filesystem, and then only store the files paths in the db, or to store the binary data of the image in a blob field.

If the pictures are big, you might also want to go one step further and store a single file across multiple db records. I've never done it myself, but I've heard that people sometimes have problems (in MySQL) loading or storing more than 1MB into a single field, so they cut the file up and store it in slices.

The second option is obviously more complex, so I'd go for the first if possible.

Thanks

naoshad — Mon, 14 Mar 2005 07:07:00 +0000

Thnaks

hank85 — Sat, 12 Mar 2005 03:59:45 +0000

What you want to do is take a look into BLOB. Binary Large Object that can hold a variable amount of data.

MySQL: BLOB:
http://dev.mysql.com/doc/mysql/en/blob.html

But it is not recommended for smaller projects like yours because the comparison work done to the actual process and ram load is greater than just storing it regularly. Not until you have very large files does it become somewhat useful.

naoshad — Wed, 02 Mar 2005 16:46:56 +0000

Thanks Busy. For your information

Busy — Mon, 28 Feb 2005 08:38:38 +0000

You dont want to save the actual image in the database, just save the images name (and details like width, height etc if you want).