johnsok
Member²
Using PLSD Version 7.0.3.1115.
When I highlight a table name in the browser, a table that is case sensitive and was created with the double-quotes (eg. "My_Tab"), the list that is generated which is ultimately passed into Oracle Export is transforming My_Tab into MY_TAB, therefore Oracle Export errors and I can't get a backup. Same thing for the SQL Inserts "export".
I see a few other posts from recent to years past regarding case sensitivity. Will this make it into the next release? Unfortunately, we have to contend with a very limited scope of an older MS Access and importing the objects into Oracle via ODBC and do not have any flexibility to modify the double-quotes. The result are case sensitive tables and columns, which are not a problem exactly (at least for our uses) other than backups.
When I highlight a table name in the browser, a table that is case sensitive and was created with the double-quotes (eg. "My_Tab"), the list that is generated which is ultimately passed into Oracle Export is transforming My_Tab into MY_TAB, therefore Oracle Export errors and I can't get a backup. Same thing for the SQL Inserts "export".
I see a few other posts from recent to years past regarding case sensitivity. Will this make it into the next release? Unfortunately, we have to contend with a very limited scope of an older MS Access and importing the objects into Oracle via ODBC and do not have any flexibility to modify the double-quotes. The result are case sensitive tables and columns, which are not a problem exactly (at least for our uses) other than backups.
