From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Darko Prenosil <Darko(dot)Prenosil(at)finteh(dot)hr> |
Cc: | Edwin Quijada <listas_quijada(at)hotmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Picture with Postgres and Delphi |
Date: | 2003-09-09 21:07:03 |
Message-ID: | Pine.LNX.4.33.0309091506410.14597-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 9 Sep 2003, Darko Prenosil wrote:
>
> ----- Original Message -----
> From: "Edwin Quijada" <listas_quijada(at)hotmail(dot)com>
> To: <pgsql-general(at)postgresql(dot)org>
> Sent: Tuesday, September 09, 2003 6:54 PM
> Subject: [GENERAL] Picture with Postgres and Delphi
>
>
> > Hi !! Everybody
> > I am developing app using Delphi and I have a question:
> > I have to save pictures into my database. Each picture has 20 o 30k aprox.
> > What is the way more optimus?
> > That 's table will have 500000 records around. Somebody said the best way
> to
> > do that was encoder the picture to field bytea but I dont know about this.
> > Another way is save the path to the picture file but I dont like so much
> > because I need to write to disk by OS and have permission to write a
> > directory to OS.
> > What do u think??
>
> You may choose between Bytea or large objects.
> I had some problems with bytea on earlier version of pg (7.2 I think), but
> last time I checked (7.3), all worked fine.
> However, I use large objects.
> The only disadvantage of large objects I see is that You can't dump them
> into textual dump. You must use binary dumps.
for portability, I've always base64 encoded and stored them as straight
text. That works well too.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera Munoz | 2003-09-09 21:20:26 | Re: to_timestamp and to_date fails in postgresql 7.1.3 |
Previous Message | Tom Lane | 2003-09-09 20:58:38 | Re: any chance of "like ANY (array[])" like the "= ANY (array[])" syntax? |