The new CoRoutine-approach seems to slow down certain ViewDefinitions (in comparison to running a Query directly).
FWIW, here's a download-link to an NorthWind-SQLite-DB, which already contains certain view-definitions: http://vbRichClient.com/Downloads/NWind.zip (an "Analyze"-command was already run against that DB). The one view-def (where the difference is most apparent) is [Invoices]: Here a: Select * From Invoices needs about 20msec. Whereas running the SQL of the View-definition directly, needs only about 10msec. A simpler view-definition in the above zipped NWind.db is: [Order Details Extended] Which is defined with the following SQL: SELECT * FROM Products JOIN [Order Details] Using(ProductID) Order By OrderID When run directly, it comes up with the result after ~4msec, whereas: Select * From [Order Details Extended] needs ~6msec. Using Explain, it showed that in case we run against the ViewNames, the CoRoutine-approach was present, whereas when running the SQL directly (and faster), the CoRoutine-preparation was absent from the Explain-Output... No biggie here so far - but reporting the behaviour early seemed like a good idea to me... Kind Regards, Olaf _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
