From: Jonathan Gardner <jgardner@jonathangardner.net>
To: "cristi" <cristi@dmhi.ct.ro>, <pgsql-sql@postgresql.org>
Subject: Re: Blobs with perl
Date: Tue, 17 Jun 2003 07:30:43 -0700
User-Agent: KMail/1.5
References: <00e001c334ae$d93e52c0$7201a8c0@aaa>
In-Reply-To: <00e001c334ae$d93e52c0$7201a8c0@aaa>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: clearsigned data
Content-Disposition: inline
Message-Id: <200306170730.44746.jgardner@jonathangardner.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 17 June 2003 02:00, cristi wrote:
> I want to insert a picture in a table from an internet browser using a
> script made in perl.
> Has somebody a code example with this kind a problem (I need only a code
> fragment)?
>

Despite PostgreSQL's powerful BLOB features, I would strongly suggest again=
st=20
storing these kind of things in the database. It is better to have it in a=
=20
local file for several reasons.

1) Apache can server up local images lightning fast
2) You can edit local images with your favorite image editor (ie, Gimp,=20
Photoshop)
3) You can ftp, scp, sftp the image around without a problem.
4) You can tar it up and archive it.
5) You can move it off of your burdened PostgreSQL database server machine =
and=20
on to its own image server when your site becomes popular.

While all of the above are certainly possible with PostgreSQL, it is a bit=
=20
more complicated.

And remember, while your database server is small now, it will grow, and gr=
ow,=20
and grow, and grow. It will one day become the bottleneck in your operation=
s.=20
That is an inevitable fact of any dynamic website.

- --=20
Jonathan Gardner <jgardner@jonathangardner.net>
(was jgardn@alumni.washington.edu)
Live Free, Use Linux!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+7yYTWgwF3QvpWNwRAv3WAKDFrjfQUpQFmZFvVMismUeoxABoDQCfY/F7
LajclhvacQOgsn+6qnLEEwQ=3D
=3Dk0vW
-----END PGP SIGNATURE-----