X-Original-To: pgsql-odbc-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 992939DCB95 for ; Thu, 8 Dec 2005 09:59:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 73260-05 for ; Thu, 8 Dec 2005 09:59:30 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by postgresql.org (Postfix) with ESMTP id 2324F9DCB81 for ; Thu, 8 Dec 2005 09:59:25 -0400 (AST) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EkMHG-0006q8-4e for pgsql-odbc@postgresql.org; Thu, 08 Dec 2005 14:57:42 +0100 Received: from 83.145.96.114 ([83.145.96.114]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 08 Dec 2005 14:57:42 +0100 Received: from Marc.Herbert by 83.145.96.114 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 08 Dec 2005 14:57:42 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-odbc@postgresql.org From: Marc Herbert Subject: Re: BLOB handling compatibility with PostgreSQL > 7.4 Date: Thu, 08 Dec 2005 14:59:23 +0100 Lines: 22 Message-ID: <871x0nr8p0.fsf@meije.emic.fr> References: <438B792D.6030802@bnl.gov> <20051206192749.GA24711@soptik.pzkagis.cz> <874q5l40fp.fsf@meije.emic.fr> <200512081055.12263.peter_e@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 83.145.96.114 User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Jumbo Shrimp, linux) Cancel-Lock: sha1:MuJr4IJRcgULQzt66DbC95mxuAs= X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=1.253 required=5 tests=[RCVD_NUMERIC_HELO=1.253] X-Spam-Score: 1.253 X-Spam-Level: * X-Archive-Number: 200512/93 X-Sequence-Number: 6572 Peter Eisentraut writes: > Marc Herbert wrote: >> Ludek Finstrle writes: >> > Type oid doesn't represent only large objects. >> >> This is IMHO the original sin. oid is overloaded as both an internal >> type and something the basic user has to play with. > > Why aren't you using bytea? Is that not supported by the ODBC driver? We are developping a middleware and are not free to choose our data types. As far as i know, the implementation of bytea and large objects in the database are totally different and I suspect there are good reasons to use either one of them, depending on the actual data and application involved.