Re: pro's and con's of storing images
| From: | Andrew Hill | Date: | Fri, 16 Feb 2001 03:40:37 +0000 |
| Subject: | Re: pro's and con's of storing images | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-40090@lists.php.net to get a copy of this message | ||
This may be getting off topic, but the only way storing images in a database
DOES make sense is if you are accessing the the database via WebDAV.
.02
Best regards,
Andrew
---------------------------------------
Andrew Hill - OpenLink Software
Director Technology Evangelism
eBusiness Infrastructure Technology
http://www.openlinksw.com
On 2/15/01 10:18 PM, "Maxim Maletsky" <maxim.maletsky@japaninc.net> wrote:
> How many times do I have to post it here ...
>
> People, store the graphics (or any other kind of uploaded and not-uploaded
> files) our of DBs, put them in some logic way in some directories so they
> are easier to use. Not in DB. In DB it will just getting slower.
>
> UNLESS there is no other solution for a problem you could have.
>
> my point: whenever it is possible to store the files in folders rather then
> DBs - store them so.
>
> Cheers,
> Maxim Maletsky
>
>
>
> -----Original Message-----
> From: Adrian Murphy [mailto:adrian.murphy@eudos.com]
> Sent: Wednesday, February 14, 2001 9:12 PM
> To: php-general@lists.php.net
> Subject: [PHP] pro's and con's of storing images
>
>
> I'm putting togeather a simple website buider app.
> i'm allowing users to upload images.I'm wondering whether i should store
> those images in a database or create dirs for each user.the mysql db has a
> relatively small capacity but storing them to the db might make it simpler
> for me.
> also ftp functions don't work on the server and my damn isp keeps fobbing me
> off when i ask him to do anything.
>