Re: [sqlite] What is the most flexible way to exact the table name from a SQL statement

On 28 Oct 2017, at 1:44pm, Shane Dev wrote: > sqlite> select * from sql; > insert into tab1 select 'example text'; > update tab2 set col2 = 123 where col2 = 1; > delete from tab3 where col1 = 2; > > For the first row, I could build a query using instr and substr

[sqlite] What is the most flexible way to exact the table name from a SQL statement

Hello, Let's say I have a table containing of SQL statements, for example sqlite> .schema sql CREATE TABLE sql(statement text); sqlite> select * from sql; insert into tab1 select 'example text'; update tab2 set col2 = 123 where col2 = 1; delete from tab3 where col1 = 2; For the first row, I

Re: [sqlite] Small Performance Regression (3.21.0)

> I for my part would *insist* on SQLite throwing an error, when it encounters unknown (userdefined) functions or collations Yes, sure, you need to know about the missing UDF or collation. I suppose there is no sensible way to know about this and still be able to run the SQL. I looked at the

Re: [sqlite] Small Performance Regression (3.21.0)

Am 28.10.2017 um 23:00 schrieb Richard Hipp: On 10/27/17, Olaf Schmidt wrote: The new CoRoutine-approach seems to slow down certain ViewDefinitions (in comparison to running a Query directly). Can you please download and try the latest "Prerelease Snapshot" from

Re: [sqlite] Small Performance Regression (3.21.0)

Am 28.10.2017 um 19:22 schrieb Bart Smissaert: This is interesting, not so much for the performance regression, but for the fact that the posted Northwind database has spaces in table names and view names. I wasn't aware this is allowed and it caused a lot of errors in my app. I have this

Re: [sqlite] Small Performance Regression (3.21.0)

On 10/27/17, Olaf Schmidt wrote: > The new CoRoutine-approach seems to slow down certain > ViewDefinitions (in comparison to running a Query directly). Can you please download and try the latest "Prerelease Snapshot" from https://sqlite.org/download.html and let me know

Re: [sqlite] Small Performance Regression (3.21.0)

This is interesting, not so much for the performance regression, but for the fact that the posted Northwind database has spaces in table names and view names. I wasn't aware this is allowed and it caused a lot of errors in my app. I have this nearly fixed now (by adding the square brackets), but I

Re: [sqlite] Small Performance Regression (3.21.0)

Am 27.10.2017 um 21:11 schrieb Richard Hipp: Thanks for the report. Do you have any other interesting, complex, or slow queries using your database that you can send me for testing purposes? With regards to the NWind.db, the Invoices-View is the one with the largest processing-time. NWind.db