RE: Date bind variable being peeked, but not used for cardinality estimate

From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
To: Kerry Osborne <kerry.osborne@xxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx L" <oracle-l@xxxxxxxxxxxxx>
Date: Tue, 22 Sep 2009 15:50:17 -0700

I agree - I did a test myself too and found that it does peek at the variables 
just fine when I run through SQL*Plus, so it looks like this is just some sort 
of problem with the application, or it's communication with Oracle (jdbc?), 
datatype conversions, etc.  I've got an SR open for it now so hopefully we'll 
figure it out soon and I'll post the answer to the list when I do.

Thanks for taking the time to test it!
Brandon


-----Original Message-----
From: Kerry Osborne [mailto:kerry.osborne@xxxxxxxxxxx]

I don't think this is an issue with a limitation on the number of bind
variables. <snip>


Privileged/Confidential Information may be contained in this message or 
attachments hereto. Please advise immediately if you or your employer do not 
consent to Internet email for messages of this kind. Opinions, conclusions and 
other information in this message that do not relate to the official business 
of this company shall be understood as neither given nor endorsed by it.
--
//www.freelists.org/webpage/oracle-l

References:
- Date bind variable being peeked, but not used for cardinality estimate
  - From: Allen, Brandon
- Re: Date bind variable being peeked, but not used for cardinality estimate
  - From: Stephane Faroult
- RE: Date bind variable being peeked, but not used for cardinality estimate
  - From: Allen, Brandon

RE: Date bind variable being peeked, but not used for cardinality estimate

Other related posts: