Tim, what is the status of this improvement?

Tomas,

<< Tim, what is the status of this improvement? >>

I will see if I can put this in 4.25 Build 7, but I can't make any promises.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<< I will see if I can put this in 4.25 Build 7, but I can't make any
promises. >>

After looking at this some more, I don't think this will make it into
DBISAM.   However, due to the way ElevateDB is architected, it can be
implemented rather easily in it, and I will do so for 1.06.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Have you added this sql improvement to latest ElevateDB?
If yes then I would like to upgrade my app from DBISAM to ElevateDB, do you have any discount for
current DBISAM customers?

Regards,
Tomas

Tomas,

<< Have you added this sql improvement to latest ElevateDB? >>

Not yet, but it is still on the list of improvements to address.  It will
most likely get picked up after the .NET data provider is done.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tomas,


<<  Have you added this sql improvement to latest ElevateDB? If yes then I
would like to upgrade my app from DBISAM to ElevateDB, do you have any
discount for current DBISAM customers? >>

I finally got a chance to look into this yesterday and I'm sorry to say that
unfortunately the optimization that I was thinking of will not work.  I was
wanting to push each individual table's conditions down into each table so
that they were both evaluated for each table individually, and then again
with the OR expression after the rows were generated for the result set.
Unfortunately, this won't work because the pushing the conditions down into
each table causes the equivalent of an AND for each condition, not an OR.

Tim Young
Elevate Software
www.elevatesoft.com