I did something similar- a web application for online employer picture
directory along with dynamic graphical output of the desk locations
throughout the company (using the GD package).
I kept the pictures in a separate directory and used links in the
database. I set up a DB trigger that took car
Denis,
Interesting, have you had any experience using a SAN
for the images? Do you know anyone that has
successfully used a SAN to store images that are
accessable to multiple servers?
I do not, however the last place I worked was in the
beginning stages of putting in a SAN. As it was
explained,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theodore Petrosky wrote:
| I am working on a project where the IT department is
| pushing really hard to have all the images in the db.
| I don't know what the agenda is. I am hopeful to come
| up with reasons either why this is good or not good.
We hav
In the same vein ...
We are at present using BLOBs to store images (but not very many) and generated
output (mostly HTML and XML). The data being stored doesn't require BLOB use
because of size; it's mostly the binary nature of the data.
Lack of satisfaction with the BLOB support (generally diffi
But... search the forums, or hope that somedoby else answers also.
Best regards,
Andy.
- Original Message -
From: "Theodore Petrosky" <[EMAIL PROTECTED]>
To: "Andrei Bintintan" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, May 06, 2004 2:46
On Thu, May 06, 2004 at 04:46:22AM -0700, Theodore Petrosky wrote:
> Thanks for the reply. Are there (in your opinion)
> reasons why you would choose to store the images in
> the db?
Transactional integrity. If there's a risk that people are
going to be deleting, &c. these images, then you can e
Thanks for the reply. Are there (in your opinion)
reasons why you would choose to store the images in
the db? My feelings are that it comes down to access.
If I store the images in the db, my only access to
these images is to retrieve the image do some work on
it and reupload it. If I store the im
I suggest to store the images on the disc and write in the db only the path.
I am using the same solution. The only problem is that I have to make the
backups separately(in my case). Also this helps more in accessing the
images, you don't have to access for each image the database, you just have
to