From: Rudi Starcevic <rudi@oasis.net.au>
Cc: pgsql-sql@postgresql.org
Subject: Re: Blobs with perl
Date: Wed, 18 Jun 2003 09:18:35 +1000
Message-ID: <3EEFA1CB.20303@oasis.net.au> (raw)
In-Reply-To: <200306170730.44746.jgardner@jonathangardner.net>
References: <00e001c334ae$d93e52c0$7201a8c0@aaa>
<200306170730.44746.jgardner@jonathangardner.net>
Hi,
For not so big applications you could consider converting the binary
image/file into text, using base64, then store the resulting text.
For example I have an app. where each member may have one or two images
on their account.
So when the user upload's their image I base64 it and store the text.
Then when we need to see the image select the text and decode it back to
binary format.
It work's well for me.
This way only text is stored. It's also handy as you don't need to worry
about file name's being the same.
It will increase the file size by about 30%.
Search the web for base64 example's, I'm sure you'll find examples to
work with.
You can email me off list if you like to see some PHP code which does this.
Cheers
Rudi.
Jonathan Gardner wrote:
>-----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 against
>storing these kind of things in the database. It is better to have it in a
>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,
>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
>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
>more complicated.
>
>And remember, while your database server is small now, it will grow, and grow,
>and grow, and grow. It will one day become the bottleneck in your operations.
>That is an inevitable fact of any dynamic website.
>
>- --
>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=
>=k0vW
>-----END PGP SIGNATURE-----
>
>---------------------------(end of broadcast)---------------------------
>TIP 8: explain analyze is your friend
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: rudi@oasis.net.au
Subject: Re: Blobs with perl
In-Reply-To: <3EEFA1CB.20303@oasis.net.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox