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 C9EBD52918 for ; Fri, 3 Jun 2005 16:11:35 -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 66498-10 for ; Fri, 3 Jun 2005 19:11:26 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 1944052864 for ; Fri, 3 Jun 2005 16:11:24 -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 j53JBMbc012006; Fri, 3 Jun 2005 15:11:22 -0400 (EDT) To: David Hinkle Cc: pgsql-interfaces@postgresql.org Subject: Re: libpq, PQExecParams and the inserting of binary data In-reply-to: References: <6424.1117820918@sss.pgh.pa.us> Comments: In-reply-to David Hinkle message dated "Fri, 03 Jun 2005 13:04:11 -0500" Date: Fri, 03 Jun 2005 15:11:22 -0400 Message-ID: <12005.1117825882@sss.pgh.pa.us> From: Tom Lane 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/16 X-Sequence-Number: 5584 David Hinkle writes: > ... That example doesn't show you how to use > any binary parameters... All the parameters are text, it only shows > you how get binary results. I think it's a huge oversight myself. Duh, you are right. Will fix that. > I could probably figure out how to use the parameters as binary, but I > have no idea what to do with the OID field. If you didn't need it for the text version, you won't need it for the binary version. The type OID is only needed if the query is such that the backend can't determine the type of the parameter symbol from context. Whether you send the parameter value as text or binary has nada to do with that. regards, tom lane