X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 3258E11F732F for ; Thu, 6 Apr 2006 03:24:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 59496-02-4 for ; Thu, 6 Apr 2006 03:24:41 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from megazone.bigpanda.com (megazone.bigpanda.com [64.147.171.210]) by postgresql.org (Postfix) with ESMTP id A578811F7372 for ; Thu, 6 Apr 2006 03:24:42 -0300 (ADT) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id E64A73509A; Wed, 5 Apr 2006 23:24:41 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id E14A835090; Wed, 5 Apr 2006 23:24:41 -0700 (PDT) Date: Wed, 5 Apr 2006 23:24:41 -0700 (PDT) From: Stephan Szabo To: "Eugene E." Cc: Peter Eisentraut , Achilleus Mantzios , pgsql-sql@postgresql.org Subject: Re: have you feel anything when you read this ? In-Reply-To: <4434A207.6010600@bankir.ru> Message-ID: <20060405224337.Y83930@megazone.bigpanda.com> References: <441EA0A7.8030601@bankir.ru> <200603201415.30719.peter_e@gmx.net> <442CC95C.1030700@bankir.ru> <20060331084503.W64402@megazone.bigpanda.com> <44324AB6.2060104@bankir.ru> <20060404071118.C19036@megazone.bigpanda.com> <4433650E.1020508@bankir.ru> <20060405071322.Y58168@megazone.bigpanda.com> <4434A207.6010600@bankir.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200604/32 X-Sequence-Number: 24841 On Thu, 6 Apr 2006, Eugene E. wrote: > Stephan Szabo wrote: > > On Wed, 5 Apr 2006, Eugene E. wrote: > > > > > >>Stephan Szabo wrote: > >> > >>>On Tue, 4 Apr 2006, Eugene E. wrote: > >>> > >>> > >>> > >>>>Stephan Szabo wrote: > >>>> > >>>> > >>>>>On Fri, 31 Mar 2006, Eugene E. wrote: > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>Peter Eisentraut wrote: > >>>>>> > >>>>>> > >>>>>> > >>>>>>>Eugene E. wrote: > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>>the problem is: you'll get this four byte sequence '\000' _instead_ > >>>>>>>>of NUL-byte anyway. > >>>>>>> > >>>>>>> > >>>>>>>What you seem to be missing is that PostgreSQL data can be represented > >>>>>>>in textual and in binary form. What you in psql is the textual form. > >>>>>>>If you want the binary form you need to select it. Then you can pass > >>>>>>>the exact bytes back and forth. > >>>>>> > >>>>>>your sentence is not true. > >>>>>>I can not select exact bytes even if i use BYTEA type > >>>>> > >>>>> > >>>>>No, that is still using the textual form. If you use PQexecParams and set > >>>>>the last argument to show you want binary data, you should get binary > >>>>>data. > >> > >>ok > >>then i am using PQexecParams > >> > >>the following tiny program shows a wonderful lameness... > > > > > > What lameness? The fact that you're trying to use a binary (network order > > maybe) integer as a string? That's not the fault of PQexecParams but > > of the code calling it. > > You're right ! > That's is not a fault of PQexecParams at all. That's the fault of its > design. No, I'd argue in this case that it was the fault of a programmer not paying enough attention/not thinking through what the api doc says. >(I pretty know why an integer has been not displayed, but why > they designed this function that way ? i do not know) What would you expect it to do given a single result format argument? If you want to propose a new function (set of functions) that have different behavior, make a coherent proposal. Statements like it should do X because I want it to aren't coherent proposals. Expect to get asked why bytea is special -- why should integer be passed as a string given that you may often want to do operations on the value which expect it as an actual number not the string representation of a number.