| From: | Scott Ribe <scott_ribe(at)killerbytes(dot)com> |
|---|---|
| To: | Jorge Godoy <jgodoy(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Database versus filesystem for storing images |
| Date: | 2007-01-08 23:19:35 |
| Message-ID: | C1C81F97.5F5B6%scott_ribe@killerbytes.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> 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
Not necessarily. It does take carefully controlling access, with a good deal
of thought and error-checking on the part of the code that has write access
to the files, but it can certainly be done.
> But if there are other people touching
> things -- moving / creating / deleting / changing files and directories --
> then things get more complicated to manage.
Absolutely. But allowing the kinds of tools mentioned earlier for examining
files does not require giving anyone write access ;-)
--
Scott Ribe
scott_ribe(at)killerbytes(dot)com
http://www.killerbytes.com/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Sales | 2007-01-08 23:39:39 | Questions about horizontal partitioning |
| Previous Message | Jeanna Geier | 2007-01-08 22:43:12 | SELECT INTO using Views? |