Re: LIBPQ Implementation Requiring BYTEA Data

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Cliff_Bytes <creid(at)eclipssolutions(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: LIBPQ Implementation Requiring BYTEA Data
Date: 2013-03-05 01:04:09
Message-ID: 51354489.7080505@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/04/2013 11:57 PM, Cliff_Bytes wrote:
> Merlin
>
> I will try your suggestion, thanks. I am somewhat surprised to find few
> hacks related to my issue. And the BYTEA type and function documentation
> leave much to be desired, IMHO, being a newbie on the Type BYTEA front.
>
One of the most helpful things you can do when you encounter things like
that is to take notes on what's giving you trouble, then come back later
once you've found out what's going on and explain what we're missing in
the documentation. The things that, if they'd been in the documentation,
would've helped you solve your problem.

I try to do this whenever I'm learning a new technology; I start a
"newbie notepad" with all the things I found confusing, underdocumented,
or generally awful. I come back to it once I've got some idea what's
going on and write it up as a constructive criticism of what docs
improvements, usability fixes, etc might make coming up to speed easier.
With patches when I get the chance.

Merlin's suggestion to use libpqtypes makes sense. I'd also look at
using PQexecParams; you should be using it pretty much all the time anyway.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Farina 2013-03-05 01:04:27 Re: Enabling Checksums
Previous Message Josh Berkus 2013-03-05 00:43:10 Re: Enabling Checksums