From: | Joe Conway <joseph(dot)conway(at)home(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | bytea/ODBC/MSAccess issue |
Date: | 2001-11-24 05:09:45 |
Message-ID: | 3BFF2B99.3060905@home.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I just discovered an issue related to one of the bytea changes in 7.2.
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.
Previously, it was not possible to create an index on a bytea column, so
this was not an issue, but now you can.
Trying to create a link to a table with an index on a bytea column, you
get an error: "Invalid field definition 'bytea_field_name' in
definition of index or relationship". I confirmed that the index was in
fact the issue by dropping it and then successfully creating the link.
Any thoughts on how to get around this, short of dropping indexes on all
bytea columns? Is their any way to suppress bytea column indexes from
view to the ODBC driver?
Thanks,
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-11-24 05:42:08 | Re: bytea/ODBC/MSAccess issue |
Previous Message | Tom Lane | 2001-11-24 03:45:26 | Re: upper and lower doesn't work with german umlaut? |