SQLite Forum

multiple queries
Login
Again, you may be able to craft a set of queries that are independent, but that cannot shape engine behaviour.

> 1.logging queries 2 5 7 9 as faulty up front & in one go is a better response than logging query 2 is faulty, then query 5 is faulty, ... etc.

Imagine that query 1 in the list created a table and query 2 then needs to insert some values into that table - actually this is a very common way to start scripts on this forum intended to explain some bug report.

Your idea that we can "check" if query 2 will fail regardless of whether query 1 failed or not becomes very obviously flawed - The Insert would fail horribly, yet if query 1 did actually succeed, query two would be perfectly executable.

This is and always has been the premise of "ERROR" generation in all software I think, stop the moment we reach something that cannot be done (and perhaps cannot be handled by any of the provided levels of error-handling).

Even your example sends chills down my spine:

> If the task were to collate daily sales data from 10 community pharmacies stopping at 2 will discard data from 9 of them, completing the loop means that data from only 4 of them is discarded.

What financial manger would OK this behaviour?  Seeing a report that only includes financials from those business units where "the query succeeded for"...

That's Enron-level math.

Fix the whole thing first, and only then use it.