Development update v2.0Beta9

[barrymavin]

I am progressing well with v2.0 and will be uploading v2.0Beta9 shortly. As always let me know if you experience any issues.

In this beta I have made some fine tuning to the SQL engine and fixed an issue whereby the SMARTQUERY cache was not being used properly on Windows.

The main benefit of SET SMARTQUERY ON is that it will cache query results persistently (even across reboots) and only throw the smartquery cache away if any of the tables involved in a query has been modified since the query was cached. For huge tables with complex joins this results in massive performance gains.

You typically use SMARTQUERY on WORM tables i.e. Write Once Read Many. If you think about it, why even bother to perform query optimization if you already have a resultset and the tables in the query have not been modified in any way for the exact same query. This is the basis of intelligent queries and that's what SMARTQUERY technology provides for you.

In this latest beta, I am now seeing SQL selects on tables containing 5,000,000 rows in <1ms.

I will be doing further work on the SQL engine to turbo charge it over the next few releases.

[naeempk]

Good news for Lianja developers. I request you to add some modifications/enhancements in Lianja ODBC driver too. I have already submitted some tickets and still waiting for the solution. Lianja ODBC driver is still not as good as other SQL ODBC drivers.

Good luck.

[barrymavin]

Hi Naeem,

Your ticket to investigate the use of transactions using ODBC is in the work queue.