Re: bytea/ODBC/MSAccess issue

> -----Original Message-----
> From: Tom Lane
> 
> Joe Conway <joseph.conway@home.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
lengthcan 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