Menu
▾
▴
#29 unsupported data type BINARY for index, making read-only
I get this when I execute SQL on an MS Access table. It does not have any Binary fields. It does not have any indexes on Binary fields. The PK is a two-column key based on meaningful text values.
None of the net searches I've performed yield any results that seems to apply to my situation.
FYI I just posted this in the help forum. That may be a better place for an initial support request. I didn't know about it this morning. I would remove this if I could see a way to do so. I'll come back here if I strike out there. But in the meantime, I don't want to pile unnecessary work in anyone's in-box.
Ticket moved from /p/jackcess/bugs/118/
i'm moving this to a feature request. i will look at quieting the warning for system tables (as i assume it is one a system table).
Would it be acceptable to lower the messages to debug if the table in question is a system table?
I have to assume that the table in question is something internal to Access if that is what you are saying. User-defined tables do not appear to be the problem. Since it does not stop production and simply acts as a warning, my goal is simply to eliminate the message. (On some level though, it must be reporting a real problem that is "invisible" to me. Maybe some system table has been rendered read only and internal housekeeping is not taking place? I don't know. As a programmer, that worries me.)
I tried running the database-fix, but that had no effect. In the end I can live with it if I had to. But if you can turn it off that would be fine. Alternately, an additional clause could be added to the message that identifies the specific table that is causing the problem -- even if it is internal. At the moment, by providing so little information, it is simply pointing to a rabbit hole, if the database-fix does not correct the problem. You could spin your wheels for hours, days, or weeks tracking it down.
i plan on adding more context to some of the error messages.
in this case, there's nothing you can do to change the situation. there are some indexes on system tables that jackcess doesn't yet understand. however, jackcess does not currently use those indexes for anything (they just get loaded when the table is loaded). so, jackcess is fully functional, but the tables are not. if you are just manipulating user tables, you won't have any problems. if, for some reason, you needed to do a lookup on one of the relevant system tables using the problematic index, then you would have a problem. that's why i hesitate to remove the log message completely.
I've lowered the log level of the relevant warnings for system tables.
i've added contextual info (db/table/column/index) to a whole lot of errors/warnings.
This is fixed in trunk and will be in the 2.0.9 release.