Re: To store or not to store . . .
| From: | Dennis Moore | Date: | Thu, 25 Apr 2002 03:30:57 +0000 |
| Subject: | Re: To store or not to store . . . | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-94502@lists.php.net to get a copy of this message | ||
If your page is frequently access and the data does not change then by all
means store the image in the file system.
however, I have found it useful to store the images in the database for
certain applications which I want to maintain an additional level of
security over the images when using sessions management. For example, if I
want certain users access to certain images. It is up to you to balance
performance with referential integrity and additional coding.
----- Original Message -----
From: "PHP List" <php_list@ibcnetwork.net>
To: "php" <php-general@lists.php.net>
Sent: Wednesday, April 24, 2002 7:45 PM
Subject: [PHP] To store or not to store . . .
> Hi,
> I was wondering about the following:
> Should I store a picture directly in a MySQL table? Or just store the link
> to a file on the system somewhere?
>
> I would think that leaving the picture as an actual file and just storing
> the link would be quicker. But what are the dis/advantages of storing
right
> in the table? I like the idea of not cluttering up my file system.
Pictures
> would only be about in the 20K range.
>
> Thanks,
> Chris
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>