Reshat Sabiq wrote:
> Then the only reasons i can see to not store images in a DB, and the
> i. If the same images also need to be accessed from a file system, such
> as by a web server, as regular URLs.
> Of these 3, only i. appears to be a realistic concern for images. It's a
> lot easier to list a URL on an [X][HT]ML page.
That's not really a problem. You can write a trivial CGI
program in your favourite language (Python, PHP, Perl or
whatever, even /bin/sh) that fetches an image from the DB,
so you can write URLs like http://.../imgfetch.cgi?foo.jpg.
You're even a lot more flexible that way, because you can
fetch images by various criteria, not just by filename.
PS: I've trimmed the "Cc:" list a bit.
Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
"Unix gives you just enough rope to hang yourself --
and then a couple of more feet, just to be sure."
-- Eric Allman
In response to
pgsql-novice by date
|Next:||From: Thilo Hille||Date: 2004-03-29 10:51:11|
|Subject: dynamic interval in plpgsql|
|Previous:||From: M. Bastin||Date: 2004-03-28 23:33:13|
|Subject: Re: Images in Database|