Received: from u1.abs.net (root@u1.abs.net [207.114.0.131]) by hub.org (8.9.2/8.9.1) with ESMTP id KAA11105 for ; Fri, 29 Jan 1999 10:24:27 -0500 (EST) (envelope-from byronn@insightdist.com) Received: from insightdist.com (nobody@localhost) by u1.abs.net (8.9.0/8.9.0) with UUCP id KAA26650 for pgsql-interfaces@postgreSQL.org; Fri, 29 Jan 1999 10:07:35 -0500 (EST) X-Authentication-Warning: u1.abs.net: nobody set sender to insightdist.com!byronn using -f Received: from ceodev by insightdist.com (AIX 3.2/UCB 5.64/4.03) id AA31871; Fri, 29 Jan 1999 09:56:29 -0500 Received: from byronn by ceodev (AIX 4.1/UCB 5.64/4.03) id AA52420; Fri, 29 Jan 1999 09:56:29 -0500 Message-Id: <36B1CC96.7FF45553@insightdist.com> Date: Fri, 29 Jan 1999 09:58:30 -0500 From: Byron Nikolaidis X-Mailer: Mozilla 4.05 [en] (Win95; I) Mime-Version: 1.0 To: markh@clockworkweb.com Cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] varchar() access References: <36b4a95d.2361109@jupiter.clockworkweb.com> <36B0B1B0.3C13B9D3@insightdist.com> <36b0fcb9.1568671@jupiter.clockworkweb.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mark Himsley wrote: > I thought Postgres had a limit of 8K? That's what it says in the docs... > Maybe, but the entire statement length also has a limit of 8K! That's where I think it gets a little ridiculous to try and use in-line sql to send/retrieve data of these sizes. The large object interface is perfect for this. I am going to try to add LongVarChar/Large Object support to the driver soon. We will need two different data types now -- one for binary (already have "lo") and one for char (maybe "lo_char"). Byron