I am out of the office until 02.01.2018.
I will reply to your message when I return.
Note: This is an automated response to your message "[h2] Re: USE INDEX
confusion with joins, v1.4.195" sent on 23.12.2017 1:25:19 PM.
This is the only notification you will receive while this person is
I'll see what I can do. Might take a little while—you know, holidays and
such...
On Saturday, December 23, 2017 at 1:30:59 PM UTC+1, Noel Grandin wrote:
>
> that sounds like an improvement, would you like to submit a PR? Perhaps
> with a test-case?
> the TestOptimisations class has a bunch of
that sounds like an improvement, would you like to submit a PR? Perhaps
with a test-case?
the TestOptimisations class has a bunch of tests for this kind of thing.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group
BTW, when appending NULLS LAST or NULLS FIRST to any of these queries, no
index is ever used for sorting. And even worse, H2 does not even do the
efficient join anymore, but uses a tablescan.
explain select A.b_id from A inner join B use index (ab) on A.b_id = B.id
where A.id = 1 order by B.a
