Re: Frustrating LO problem

From: Sean Murphy <Sean(dot)Murphy(at)equipoint(dot)com>
To: "Andy Shellam (Mailing Lists)" <andy(dot)shellam-lists(at)mailnetwork(dot)co(dot)uk>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Frustrating LO problem
Date: 2007-01-03 16:11:58
Message-ID: 459BD5CE.6040309@equipoint.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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.
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Alagarsamy Manimaran-FDRP63 2007-01-03 19:50:21 Need help. Postgres log for prepared statements.
Previous Message Tom Lane 2007-01-03 16:03:27 Re: Trigger trouble