From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joe Conway" <joseph(dot)conway(at)home(dot)com> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: bytea/ODBC/MSAccess issue |
Date: | 2001-11-25 21:34:49 |
Message-ID: | EKEJJICOHDIEMGPNIFIJAEELGAAA.Inoue@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Tom Lane
>
> Joe Conway <joseph(dot)conway(at)home(dot)com> writes:
> > When creating a linked table in MS Access, bytea columns get mapped to
> > "OLE Object" as a datatype, and this type is not able to be indexed.
>
> Could we make our ODBC driver map bytea to some datatype that Access
> doesn't choke on?
IIRC our ODBC driver maps bytea to SQL_VARBINARY which is
able to be indexed in MS Access. Probably Joe is changing the
*Max Varchar* option > 255.
Currently the mapping of our driver is
SQL_VARBINARY (the length <= 255) <---> bytea
SQL_LONGVARBINARY (the length can be > 255) <---> lo
.
MS Access couldn't handle the binary type index > 255 bytes.
PostgreSQL hasn't been able to have indexes on bytea until
quite recently and bytea is unavailable for LO.
Every application has its limitation.
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2001-11-25 22:19:45 | Re: RPMs and regression tests (was Re: v7.2b3 packaged...) |
Previous Message | Ian Barwick | 2001-11-25 19:17:41 | Re: Security note: MS SQL is current worm vector |