Re: Mixed Case names in 8.1.6 via ODBCC

From: Howard J. Rogers <howardjr_at_www.com>
Date: Mon, 2 Oct 2000 16:59:47 +1000
Message-ID: <39d823c2@news.iprimus.com.au>

Well, I've just a transfer from Access to 8.16 via ODBC, and the usual rules applied:

select * from Table; -failed miserably... no such object exists select * from 'Table' -worked fine.

And then I remembered I'd be a looney to do this for the rest of my life, and changed the Access source so that all its tables and fieldnames were in uppercase to start with. Makes life much simpler.

But: the answer to your question? No, Oracle hasn't de-supported it in 8.1.6, 'cos it worked just fine for me.

Regards
HJR
-

Opinions expressed are my own, and not those of Oracle Corporation Oracle DBA Resources: http://www.geocities.com/howardjr2000

<eseckler_at_my-deja.com> wrote in message news:8qvin9$16h$1_at_nnrp1.deja.com...
> Has Orale dropped support for mixed case table and column names? I'm
> having a problem using Oracle 8.1.6 with my ODBC application. All of
> the catalog functions I've tried fail to return any rows if a mixed
> case table or column name is specified. The same functions return rows
> (on the same databases) if I use the 8.0.5 client and driver.
> Specifically SQLTables, SQLColumns, and SQLStatistics have been tried.
> Is this a known bug? Does anyone else use Mixed (or lower) case names
> with Oracle?
>
> Is there a way to see what the SQL is that is getting to the server?
> I'd like to see what the ODBC driver / Oracle Client is sending to the
> Oracle server.
>
> I'm also having a problem inserting a row into a table with a
> BLOB column. I get an invalid column error on the insert but the
> column name works fine on the select. Any idea what could be wrong
> here?
>
> Any help would be greatly appreciated.
>
> Sincerely,
> Ed Seckler
>
>
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Mon Oct 02 2000 - 01:59:47 CDT