Re: Database versus filesystem for storing images

From: Jorge Godoy <jgodoy(at)gmail(dot)com>
To: Andrew Chernow <pg-job(at)esilo(dot)com>
Cc: Jorge Godoy <jgodoy(at)gmail(dot)com>, Jeremy Haile <jhaile(at)fastmail(dot)fm>, pgsql-general(at)postgresql(dot)org
Subject: Re: Database versus filesystem for storing images
Date: 2007-01-06 01:33:32
Message-ID: 87y7ohey6r.fsf@ieee.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Andrew Chernow <pg-job(at)esilo(dot)com> writes:

> depends on how you do it. not everything has to go in a database to be
> reliable. Part of good engineering is realizing when to use a tool and when
> not to.
>
> I think a 10K view of the issue is in order. The bigger picture is being
> missed, or I am not communicating well.
>
> I bet if I gave you a million dollars, you could implement what I proposed;
> in a reliable, redundant fasion. You could probably convince anyone of its
> merits, making my case for me. All you would have to do is entertain the
> idea ... I mean you sound smart enough ... probably smarter than me :)

LOL. :-) This proposal was made to Demi Moore and her marriage ended in a
disaster... ;-)

My point is: if I need to be 100% sure that what is referenced on the database
is accessible all the time when the reference is, then I need to have this on
the database; if it can be missed sometimes then using the filesystem is
acceptable.

I'd include on the "100%" category fiscal records, client's documents, company
projects, etc. On the second the drawing the user made of his grandmother,
the picture of the pretty neighbor in the shower, all reports generated
automatically from data existing on the database itself, etc.

I have systems with both solutions and the ones that give me more trouble to
manage are the ones that use external files. If nobody has access to the
server, then it is a piece of cake. But if there are other people touching
things -- moving / creating / deleting / changing files and directories --
then things get more complicated to manage. Inside the DB they usually don't
dare to touch things because they know that they might destroy very important
data. It is something that is inherent to people that everything the board of
directors use might cost their job. Even if it is just the coffee
plate... :-)

Anyway, do you need my account number? ;-) You can leave the transfer charges
to me, after all friends do that ;-)

And I am not smarter than anyone that listen to and learn with other people.
I am still learning here since I'm really a newbie in this database world.
Thanks for that, though :-)

--
Jorge Godoy <jgodoy(at)gmail(dot)com>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-01-06 01:40:37 Re: losing my large objects with Postgresql 8.1.4 and 8.1.5
Previous Message nyenyec 2007-01-06 01:29:13 Re: GUI tool that can reverse engineering schemas