pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedR: Re: Import image into postgresql database
2+ messages / 2 participants
[nested] [flat]
* R: Re: Import image into postgresql database
@ 2011-07-01 12:30 francescoboccacci@libero.it <francescoboccacci@libero.it>
0 siblings, 1 reply; 2+ messages in thread
From: francescoboccacci@libero.it @ 2011-07-01 12:30 UTC (permalink / raw)
To: Gabriele.Bartolini@2ndQuadrant.it; +Cc: pgsql-admin
Thanks,
Francesco
>----Messaggio originale----
>Da: Gabriele.Bartolini@2ndQuadrant.it
>Data: 01/07/2011 12.27
>A: <francescoboccacci@libero.it>
>Cc: <pgsql-admin@postgresql.org>
>Ogg: Re: [ADMIN] Import image into postgresql database
>
> Ciao Francesco,
>
> On Fri, 1 Jul 2011 12:13:33 +0200 (CEST), "francescoboccacci@libero.it"
> <francescoboccacci@libero.it> wrote:
>> I tried to insert in both ways. With oid type i able to insert
>> images, but
>> with bytea i don't understand how store it .
>
> I would definitely suggest to use 'bytea' column rather than large
> objects support in PostgreSQL, as it is much simpler to manage.
>
>> INSERT INTO images (img) VALUES (pg_escape_bytea('C:\\9999.jpg'))
>
> bytea is an array of bytes, it is like a binary string. You must
> provide directly the binary content yourself in your SQL query
> (PostgreSQL does not have a clue about where your locale file is).
>
> Loading must be performed at client level, using your favourite
> application language, then passed to PostgreSQL. Every major language
> now is able to deal with PostgreSQL's bytea type transparently.
> Otherwise, you can still do it yourself, by properly formatting every
> input byte in your SQL query using the format described here:
> http://www.postgresql.org/docs/9.0/static/datatype-binary.html
>
>> but it doesn't work.
>> So How can i solve my problem? and another question.. If i able to
>> store my
>> image into bytea fiels..how can i export it for see it for example
>> with paint?
>
> You still have to think in terms of binary information, sequences of
> bytes. Your application might return it via the web (typical case) or
> save it locally in a temporary folder for display.
>
> Ciao,
> Gabriele
>
>--
> Gabriele Bartolini - 2ndQuadrant Italia
> PostgreSQL Training, Services and Support
> Gabriele.Bartolini@2ndQuadrant.it - www.2ndQuadrant.it
>
>--
>Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-admin
>
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: R: Re: Import image into postgresql database
@ 2011-07-11 14:26 David Hornsby <david@beechglen.com>
parent: francescoboccacci@libero.it <francescoboccacci@libero.it>
0 siblings, 0 replies; 2+ messages in thread
From: David Hornsby @ 2011-07-11 14:26 UTC (permalink / raw)
To: pgsql-admin
The best way I found is to just treat the image as a BLOB. Create a
column with type OID and do a lo_import and an lo_export as demonstrated
in this page.
http://www.postgresql.org/files/documentation/books/aw_pgsql/node96.html
-David.
On 7/1/11 8:30 AM, francescoboccacci@libero.it wrote:
> Thanks,
>
> Francesco
>
>> ----Messaggio originale----
>> Da: Gabriele.Bartolini@2ndQuadrant.it
>> Data: 01/07/2011 12.27
>> A:<francescoboccacci@libero.it>
>> Cc:<pgsql-admin@postgresql.org>
>> Ogg: Re: [ADMIN] Import image into postgresql database
>>
>> Ciao Francesco,
>>
>> On Fri, 1 Jul 2011 12:13:33 +0200 (CEST), "francescoboccacci@libero.it"
>> <francescoboccacci@libero.it> wrote:
>>> I tried to insert in both ways. With oid type i able to insert
>>> images, but
>>> with bytea i don't understand how store it .
>> I would definitely suggest to use 'bytea' column rather than large
>> objects support in PostgreSQL, as it is much simpler to manage.
>>
>>> INSERT INTO images (img) VALUES (pg_escape_bytea('C:\\9999.jpg'))
>> bytea is an array of bytes, it is like a binary string. You must
>> provide directly the binary content yourself in your SQL query
>> (PostgreSQL does not have a clue about where your locale file is).
>>
>> Loading must be performed at client level, using your favourite
>> application language, then passed to PostgreSQL. Every major language
>> now is able to deal with PostgreSQL's bytea type transparently.
>> Otherwise, you can still do it yourself, by properly formatting every
>> input byte in your SQL query using the format described here:
>> http://www.postgresql.org/docs/9.0/static/datatype-binary.html
>>
>>> but it doesn't work.
>>> So How can i solve my problem? and another question.. If i able to
>>> store my
>>> image into bytea fiels..how can i export it for see it for example
>>> with paint?
>> You still have to think in terms of binary information, sequences of
>> bytes. Your application might return it via the web (typical case) or
>> save it locally in a temporary folder for display.
>>
>> Ciao,
>> Gabriele
>>
>> --
>> Gabriele Bartolini - 2ndQuadrant Italia
>> PostgreSQL Training, Services and Support
>> Gabriele.Bartolini@2ndQuadrant.it - www.2ndQuadrant.it
>>
>> --
>> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-admin
>>
>
>
--
David Hornsby
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2011-07-11 14:26 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2011-07-01 12:30 R: Re: Import image into postgresql database francescoboccacci@libero.it <francescoboccacci@libero.it>
2011-07-11 14:26 ` David Hornsby <david@beechglen.com>
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