Re: Storing small image files

From: Karl Denninger <karl(at)denninger(dot)net>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, pgsql-general(at)postgresql(dot)org, Nelson Green <nelsongreen84(at)gmail(dot)com>
Subject: Re: Storing small image files
Date: 2013-05-09 16:41:51
Message-ID: 518BD1CF.3070305@denninger.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 5/9/2013 11:34 AM, Alvaro Herrera wrote:
> Karl Denninger escribió:
>
>>> To encode:
>>>
>>>
>>> write_conn = Postgresql communication channel in your software that is
>>> open to write to the table
>>>
>>> char *out;
>>> size_t out_length, badge_length;
>>>
>>> badge_length = function-to-get-length-of(badge_binary_data); /* You
>>> have to know how long it is */
>>>
>>> out = PQescapeByteaConn(write_conn, badge_binary_data, badge_length,
>>> &out_length); /* Convert */
>>>
>>> That function allocates the required memory for the conversion.
> I think you're better off with PQexecParams() so that you don't have to
> encode the image at all; just load it in memory and use it as a
> parameter.
>
Yeah, you can go that route too.

--
Karl Denninger
karl(at)denninger(dot)net
/Cuda Systems LLC/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Nelson Green 2013-05-09 17:05:06 Re: Storing small image files
Previous Message Alvaro Herrera 2013-05-09 16:34:33 Re: Storing small image files