Re: Table and column with same name, fails only if using bind parameter

"Larry Leonard" <Spam_at_DefinitiveSolutions.com> wrote in message news:27270a53.0302040515.1667e314_at_posting.google.com...
> I have a table called PRICING_LEVEL, which also has a column called
> PRICING_LEVEL. (No, I'm not the one that did this.)
>
> The problem is, while this correctly returns the one row I expect:
>
> SELECT description
> FROM pricing_level
> WHERE pricing_level.pricing_level = '41';
>
> ... this always incorrectly returns zero rows:
>
> SELECT description
> FROM pricing_level
> WHERE pricing_level.pricing_level = :p_price_lev;
>
> That is, when I use bind parameters, it fails to return the correct
> row; no error is generated. Interestingly, it fails using either a
> CRecordset-derived class (ODBC), or an ODynaset-derived class (oo4o).

[Quoted] [Quoted] What happens if you use sqlplus? IF you can replicate it in sqlplus I'd suggest you consider logging a tar with oracle support.

--
Niall Litchfield
Oracle DBA
Audit Commission UK