Re: [sqlite] sqlite-users Digest, Vol 70, Issue 21

Paul Bainter wrote: > > Not sure the first two questions really matter. What matters is that the > application will not access the SQLite database before installing > System.Data.SQLite and will work after the installation. > The system might not have the required Visual C++ Runtime

[sqlite] When does SQLite DB file get locked?

Hi, I started writing this message and then read http://www.sqlite.org/lang_transaction.html, and I think I've gotten my answer, but I will ask the question to be absolutely certain, particularly when using SQLite with PHP (using PDO). Probably based on flawed understanding of how SQLite worked,

Re: [sqlite] sqlite-users Digest, Vol 70, Issue 21

Thank you for looking at my mystery question. Not sure the first two questions really matter. What matters is that the application will not access the SQLite database before installing System.Data.SQLite and will work after the installation. I have always had in my app.config the lines exactly

Re: [sqlite] SELECT and UPDATE?

Thanks (to other repliers too), That put me on the right track. -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Keith Medcalf Sent: October-18-13 7:34 PM To: General Discussion of SQLite Database Subject: Re: [sqlite] SELECT

Re: [sqlite] ORDER BY DESC after GROUP BY not using INDEX - intentionally?

Thanks. I think using GROUP BY without aggregates is a strange way to remove duplicates, anyway. Not intentional. SQLite simply fails to recognize that by using the GROUP BY in descending order it could avoid the ORDER BY clause. This is an optimization that we have never considered because it

Re: [sqlite] ORDER BY DESC after GROUP BY not using INDEX - intentionally?

Fabian Büttner wrote: > Hi, > > I have been thinking about a question on stackoverflow > (http://stackoverflow.com/questions/19236363/select-distinct-faster-than-group-by), > where some SQL framework removes duplicates from results using GROUP BY > instead of DISTINCT. > I don't want to discuss

Re: [sqlite] ORDER BY DESC after GROUP BY not using INDEX - intentionally?

On Mon, Oct 21, 2013 at 5:27 AM, Fabian Büttner wrote: > Hi, > > I have been thinking about a question on stackoverflow ( > http://stackoverflow.com/**questions/19236363/select-** >

[sqlite] ORDER BY DESC after GROUP BY not using INDEX - intentionally?

Hi, I have been thinking about a question on stackoverflow (http://stackoverflow.com/questions/19236363/select-distinct-faster-than-group-by), where some SQL framework removes duplicates from results using GROUP BY instead of DISTINCT. I don't want to discuss that this might not be a good

[sqlite] SQLITE_OMIT_FLAG_PRAGMAS issue: sqlite3_busy_timeout() called for all flag pragmas

SQLite 3.8.1 compiled with SQLITE_OMIT_FLAG_PRAGMAS #defined calls sqlite3_busy_timeout() for all flag pragmas. Example: PRAGMA legacy_file_format=100; should do nothing but sets sqlite3_busy_timeout(db, 100); The change was introduced here: