If I set the property loadIndices to true I get the following error.
java.sql.SQLException: Can't parse index expression UPPER(table)
'table' here is a column name from a legacy database.
This is on a Visual FoxPro database (not sure of the version 7-9).
|
>java.sql.SQLException: Can't parse index expression UPPER(table)
table is a reserved word in sql. Maybe you can consider removing that index file.
|
I can't.
I'm accessing a legacy database which I cannot change.
Couldn't the index parsing expression code be updated to automatically quote all column references?
|
>I'm accessing a legacy database which I cannot change.
Then we have to modify sql engine to allow table as column name if it's necessary. Why there're a table column in a table?
>Couldn't the index parsing expression code be updated to automatically quote all column references?
Yeah. It can
|
>> I'm accessing a legacy database which I cannot change.
> Then we have to modify sql engine to allow table as column
> name if it's necessary. Why there're a table column in a table?
The table is called 'sysgenpk' and it has two columns 'table' and 'currant'.
It appears that there is a row for each table in the database which
contains the next primary key for that table.
>> Couldn't the index parsing expression code be updated to automatically
>> quote all column references?
> Yeah. It can
Great!
|
I've found another table with an index parsing problem.
The table is called 'rsloddtl' and it has a column named 'drop' and an index expression "drop".
This stands for Routing/Shipping Load Detail and this is a "trucking drop" rather than an "sql drop".
Without quoting the index expression 'drop' will cause obvious problems as well.
|