From: | "Jean-Yves F(dot) Barbier" <12ukwn(at)gmail(dot)com> |
---|---|
To: | Didier Gasser-Morlay <didiergm(at)gmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: bytea and text |
Date: | 2009-11-29 06:55:40 |
Message-ID: | 4B121AEC.2010508@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Didier Gasser-Morlay a écrit :
> I hope you won't mind if I had my 2 cents to this conversation; aside
> from the actual format, this question comes up with regularity on
> various database lists.
>
> I have never understood the need for storing images inside a database
> (and to some extend blob data) because:
> - being a blog you do not query it just store and retrieve, you rarely
> update, so the need for a fancy SQL and DB engine is somewhat limited;
this is not a blog, but pictures aren't updated
> - storing images is heavy, makes the database grow, thus makes
> backup/restore that bit more painful and possibly that bit less stable. ..
^^^^^^^^^^^^^^^^^^^^
?
> For years I designed system for picture libraries where numbers like 10s
> of thousands to millions of images are common place, we would never have
> contemplated to store images on anything more complex than a file
> system. using the database to store a URL to that resource.
hmmmm, just a one shot backup for "just users".
I'm not going to feed this troll, this is MY choice.
--
Being stoned on marijuana isn't very different from being stoned on gin.
-- Ralph Nader
From | Date | Subject | |
---|---|---|---|
Next Message | Didier Gasser-Morlay | 2009-11-29 07:23:31 | Re: bytea and text |
Previous Message | Didier Gasser-Morlay | 2009-11-29 06:50:10 | Re: bytea and text |