X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 7910252854
	for <pgsql-interfaces-postgresql.org@localhost.postgresql.org>;
	Sat,  4 Jun 2005 11:57:50 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 63705-07
	for <pgsql-interfaces-postgresql.org@localhost.postgresql.org>;
	Sat,  4 Jun 2005 14:57:42 +0000 (GMT)
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by svr1.postgresql.org (Postfix) with ESMTP id 8039D52838
	for <pgsql-interfaces@postgresql.org>;
	Sat,  4 Jun 2005 11:57:40 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j54EvgEk026432;
	Sat, 4 Jun 2005 10:57:42 -0400 (EDT)
To: Volkan YAZICI <volkan.yazici@gmail.com>
Cc: Daniel Verite <daniel@manitou-mail.org>,
	pgsql-interfaces@postgresql.org
Subject: Re: libpq, PQExecParams and the inserting of binary data 
In-reply-to: <7104a737050604065267a108b@mail.gmail.com> 
References: <7104a73705060401222c6cc5d2@mail.gmail.com>
	<20050604153734.8397528@uruguay>
	<7104a737050604065267a108b@mail.gmail.com>
Comments: In-reply-to Volkan YAZICI <volkan.yazici@gmail.com>
	message dated "Sat, 04 Jun 2005 16:52:27 +0300"
Date: Sat, 04 Jun 2005 10:57:42 -0400
Message-ID: <26431.1117897062@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL
X-Spam-Level: 
X-Archive-Number: 200506/22
X-Sequence-Number: 5590

Volkan YAZICI <volkan.yazici@gmail.com> writes:
> So, this means, user _has_to_ specify the size of input while using
> binary data.

You expected something different?  libpq could hardly assume that
strlen() is the way to find out the length of a binary parameter.

			regards, tom lane