Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 4591D9F9312 for ; Wed, 3 Jan 2007 12:12:24 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 85776-03 for ; Wed, 3 Jan 2007 12:12:11 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail.hfn.net (mail.hfn.net [207.88.204.180]) by postgresql.org (Postfix) with ESMTP id 99E6F9FA18F for ; Wed, 3 Jan 2007 12:12:16 -0400 (AST) Received: from [192.168.120.85] ([67.108.63.204]) by mail.hfn.net (Ultimate Mail Server v1.0) with ASMTP id IRP53104; Wed, 3 Jan 2007 08:12:04 -0800 Message-ID: <459BD5CE.6040309@equipoint.com> Date: Wed, 03 Jan 2007 08:11:58 -0800 From: Sean Murphy MIME-Version: 1.0 To: "Andy Shellam (Mailing Lists)" , pgsql-admin@postgresql.org Subject: Re: Frustrating LO problem References: <4595B018.3090600@equipoint.com> <4595B79A.2020304@mailnetwork.co.uk> In-Reply-To: <4595B79A.2020304@mailnetwork.co.uk> X-Enigmail-Version: 0.94.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50 X-Spam-Level: X-Archive-Number: 200701/13 X-Sequence-Number: 24169 Thanks Andy, The type was declared and the column was defined as lo... after my big long explanation about how everything was identical, turns out that it wasn't... on closer examination I discovered that I had mistakenly set the ByteaAsLongVarBinary flag on in the ODBC setup for the db where it wasn't working (it was, of course, off for the db that was working) Set the flag to off and everything works fine 'n dandy. Andy Shellam (Mailing Lists) wrote: > Hi Sean, > > I'm certainly not a PostgreSQL expert when it comes to large objects > etc, but there's one thing that jumps out at me here (perhaps someone > else can see the same line of thought and into more depth as I can't > think of much else to suggest?) > >> The logfile lines when it doesn't: >> { >> WARNING: nonstandard use of \\ in a string literal at character 94 >> HINT: Use the escape string syntax for backslashes, e.g., E'\\'. >> LOG: statement: insert into doc.templates (description, last_update, >> template) values ('test', '12/29/2006', 'testfile\\056contents') >> ERROR: invalid input syntax for type oid: "testfile\056contents" >> > ^^ here it seems to be thinking that column 'template' is of type 'oid', > not 'lo' (if I'm reading the error right: "invalid input syntax for > type oid"). > > Just double-check what data-type that column is in this database. > > Regards, > > Andy. >