Re: storing C binary array in bytea via libpq

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tom DalPozzo <t(dot)dalpozzo(at)gmail(dot)com>
Cc: pgsql-general(at)postgreSQL(dot)org
Subject: Re: storing C binary array in bytea via libpq
Date: 2016-12-06 18:49:30
Message-ID: 23460.1481050170@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

[ please keep the list cc'd ]

Tom DalPozzo <t(dot)dalpozzo(at)gmail(dot)com> writes:
> To be honest, I didn't know or I forgot about multiple VALUES in one
> command! Thanks for reminding!
> As for the PQexecParams, should I specify something in const Oid
> *paramTypes parameter? Or just something like $1::bytea?

You can do it either way. Hard-wiring the type OID will be a bit faster
than making the server parse a ton of repetitive cast constructs, but on
the other hand it means you have a magic number in your program. It's
unlikely the OID assigned to bytea would ever change, but the technique
doesn't scale well to user-defined types. Take your choice.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rich Shepard 2016-12-06 18:50:51 Re: PDF files: to store in database or not
Previous Message Joshua D. Drake 2016-12-06 18:34:06 Re: PDF files: to store in database or not