Re: pg_lo_import alternative ...

Hi,

We are developing a management software for our clients. This software si
already used for a year. The database dump is around 40MB(zipped around 10).
Our clients receive every day between 100 - 200 photos(size between
80-200kB). For the moment they have around 30000 photos, the overall size of
photos is around 5 GB. We decided that we do not put these photos in the
database, we store it on the disk. In the database we store only the
"realname" and the "storage path" of the photos and some additional info.

Yes it is true, that things may become complicated if a photo is erased or
think also to a backup to the photos. But this comes in the hand of the
administrator.

I tried first also to put the photos in the database, but I gave up on this
ideea. I think I have the code "somewhere"... have to search it it's already
1 year old....if somebody needs it just say.

Best regards.
Andy.

----- Original Message -----
From: "Rudi Starcevic" <rudi(at)oasis(dot)net(dot)au>
To: <pgsql-admin(at)postgresql(dot)org>
Sent: Thursday, November 27, 2003 6:51 AM
Subject: Re: [ADMIN] pg_lo_import alternative ...

> Hi,
>
> > Anyone that that is using Postgres for storage and retrival of
> > images please post your experiences.
>
> I've been very happy with a web application I built which stores
> images in Postgresql in text format. I use PHP to base_64 encode
> the binary image file into a text string and store that.
>
> I can send you a PHP class which I use to encode/decode the
> images and inserts them into a table.
> Email me off list if your keen.
>
> Cheers
> Rudi.
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend