I added the hint, now I don't see the rownum things at all in my paging queries. What's actually happening here, would all rows be brought back into memory or is JDBC filtering them out?
I suspect I have some bad stats somewhere that are causing the CBO to go nuts with the first_rows on, and I just need to figure out which one and tweak it. That would be preferable to me than making such a large change globally in our app, unless of course I could tell Eclipselink to use rownum filtering, just without the hint....
./tch
<mailto:
tom.ware@xxxxxxxxxx>> wrote:
Hi Tim,
Try using a session customizer and calling:
((DatabasePlatform)session.__
getDatasourcePlatform()).__
setShouldUseRownumFiltering(__
false)
-Tom
Tim Hollosy wrote:
We've run into a situation where the FIRST_ROWS hint is
causing major pain, selecting against a view. Worked fine on
our 10g database, production is 9i though and it's just
dying on 9i, any clue on how to tell eclipselink to leave
the hint out? When I leave it out, the query runs fine. I
saw a post from 2009 that said it wasn't possible to disable
it without modifying EL source.
As an alternative, any oracle wizards now how I might tell
Oracle to ignore that hint?
Thanks,
Tim
------------------------------
__----------------------------
--__------------
______________________________
___________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
<mailto: