Re: "lo" large object

From: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>, pgsql-general(at)postgresql(dot)org
Subject: Re: "lo" large object
Date: 2002-09-25 20:26:10
Message-ID: 20020925212610.C9603@quartz.newn.cam.ac.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Sep 25, 2002 at 04:11:24PM -0400, Tom Lane wrote:
> Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> writes:
> > lo being the type to keep psqlodbc happy when importing M$ access files. The
> > old definition was:
>
> > CREATE TYPE lo (
> > INTERNALLENGTH = 4,
> > INPUT = int4in,
> > OUTPUT = int4out,
>
> Hm. The system doesn't tolerate type cheats like that anymore
> (and the code was wrong anyway, since it should've been using
> oidin/oidout).
>
> I guess we'll have to fix the contrib/lo module. Thanks for the
> report...

I didn't know about contrib/lo - the above was in a FAQ - I think where
you get the psqlodbc driver from..

Cheers,

Patrick

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Patrick Welche 2002-09-25 20:30:15 Relation 0 does not exist
Previous Message Michael Paesold 2002-09-25 20:21:24 Re: Getting current transaction id