FWIW, this sounds similar to the problems you and I had (separately) a
couple of years ago:
https://groups.google.com/forum/#!topic/sqlalchemy/kv7BqWZr9KQ
https://groups.google.com/forum/#!topic/sqlalchemy/k_9ZGI-e85E
On Monday, September 12, 2016 at 5:39:37 PM UTC-4, Thierry Florac wrote:
>
> I
I don't think it's so easy to produce a test case...
Generaly speaking, indexes are used in a normal way!
There's only in a single case, for a single table, that they are not used
even for common operations. Maybe it's a statistics problem or something
else I don't understand; and AFAIK the
I'd try to see on the cx_oracle list if you can produce a self-contained
cx_Oracle-only test case and illustrate that indexes are not being
used...I think this comes up a lot over there it's like an OCI thing.
On 09/12/2016 03:20 PM, Thierry Florac wrote:
Hi Mike,
I really agrea with you
Hi Mike,
I really agrea with you on all the points you mentionned. And I won't add
anything about the cost of an Oracle database license and administrators
compared with their performances! But I actually don't have the choice...
:-/
My problem is clearly a database problem at first! But as my
Hi,
I'm working with an Oracle database which, for a reason I can't understand,
doesn't want to use indexes when working on a given table (which is quite
large) with prepared statements!
I know I can use literal columns when running "select" queries (using the
"literal_column" function), so that
