Re: [sqlite] Android SQLite 3.8.2 issue with triggers & constraints

Thanks, Dan, that does the trick. I didn't know that sqlite used any temporary files that weren't based on the database filename, but that makes perfect sense. Cheers, Doug On Wed, Jan 1, 2014 at 1:52 PM, Dan Kennedy wrote: > On 12/31/2013 10:03 PM, Douglas Orr wrote: >

Re: [sqlite] Error 11 after doing a lot of simple insert/update operations!

Woody Wu wrote: > Hi, Simon > > I upload the source code onto my dropbox: > https://www.dropbox.com/s/9shhshi0wn3e717/downloadfile.c Please have a > look at it. > > The same test program run without a problem on my pc Linux after complied > natively. But I think I should not dout my

[sqlite] SQLite3 and EINTR

Hi, If I send signals to a process that is running an sqlite query on a DB in WAL mode I get an SQLITE_BUSY error. I did set a busy handler, and the timeout hasn't elapsed yet, so it appears that EINTR is treated as an error and not retried, although I haven't tracked down exactly where. I

Re: [sqlite] Error 11 after doing a lot of simple insert/update operations!

Hi, List To make it easy to review, I've make the test code as an single c file and removed some unrelated code from the previous version. Could you so kind to point out potential problems in it, or tell me what else things I could get to check in the code or in my environment.

Re: [sqlite] [sqlite-dev] sqlite3 db is locked

Simon Slavin wrote: > On 1 Jan 2014, at 7:43am, Alexander Syvak wrote: > >> The code in function from the 1st e-mail is used before exiting, so the >> sqlite3_close is called in fact. > > Please do not cross-post between sqlite-dev@ and sqlite@. If you need to > move

Re: [sqlite] [sqlite-dev] sqlite3 db is locked

On 2 Jan 2014, at 2:57pm, Yuriy Kaminskiy wrote: > Simon Slavin wrote: >> sqlite3_busy_timeout() > > Waiting for timeout *cannot* fix any errors that can trigger failure in > sqlite3_close. Those are *program logic* errors. I am not trying to fix your program logic errors.

Re: [sqlite] "Common Table Expression"

Hello, When bigger brains created CTEs in SQL:99, I suppose they discussed a long moment the technical merit of CTEs. In my own experience : - the maintenance burden of my queries dropped significantly because of them, - I stopped harrassing (myself or a central database administrator) for views

Re: [sqlite] "Common Table Expression"

(sorry keyboard fall on the floor) Now : - I wouldn't let someone use SQL without allowing him to use CTE, - I need to use ubiquitous SQL motors, which are only TWO on windows (Access and SQLite) , and they still don't have CTE. ___ sqlite-users mailing

Re: [sqlite] [sqlite-dev] sqlite3 db is locked

Simon Slavin wrote: > On 2 Jan 2014, at 2:57pm, Yuriy Kaminskiy wrote: > >> Simon Slavin wrote: >>> sqlite3_busy_timeout() >> Waiting for timeout *cannot* fix any errors that can trigger failure in >> sqlite3_close. Those are *program logic* errors. > > I am not trying to fix

Re: [sqlite] [patch][rebase for 3.8.2] really move "const" check out of loop "WHERE const" (and "WHERE const AND expr" optimization)

Please verify that the alternative optimization checked-in at http://www.sqlite.org/src/info/b7e39851a7 covers all of the cases that you identify below. Tnx. On Thu, Jan 2, 2014 at 9:25 AM, Yuriy Kaminskiy wrote: > On 2013/11/04 Yuriy Kaminskiy wrote: > > On 2012/04/08 Yuriy

[sqlite] SQLITE_OPEN_NOMUTEX

Hi, As per documentation opening a database with SQLITE_OPEN_NOMUTEX flag opens it in multi-threaded mode. http://www.sqlite.org/threadsafe.html says In this mode, SQLite can be safely used by multiple threads provided that no single database connection is used simultaneously in two or more

Re: [sqlite] SQLITE_OPEN_NOMUTEX

On Thu, Jan 2, 2014 at 1:23 PM, Prakash Reddy Bande wrote: > Hi, > > As per documentation opening a database with SQLITE_OPEN_NOMUTEX flag > opens it in multi-threaded mode. > http://www.sqlite.org/threadsafe.html says In this mode, SQLite can be > safely used by multiple

Re: [sqlite] SQLite 2013 retrospective

Whish list for 2014 = . a simplified implementation of "Common Table Expressions", . amazing SQlite4 performance when in ":memory:". ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [patch][rebase for 3.8.2] really move "const" check out of loop "WHERE const" (and "WHERE const AND expr" optimization)

Richard Hipp wrote: > Please verify that the alternative optimization checked-in at > http://www.sqlite.org/src/info/b7e39851a7 covers all of the cases that you > identify below. Tnx. Maybe I overlooked something, but from first look it cannot handle placeholders and constant functions, and my

Re: [sqlite] [patch][rebase for 3.8.2] really move "const" check out of loop "WHERE const" (and "WHERE const AND expr" optimization)

On Thu, Jan 2, 2014 at 3:25 PM, Yuriy Kaminskiy wrote: > Richard Hipp wrote: > > Please verify that the alternative optimization checked-in at > > http://www.sqlite.org/src/info/b7e39851a7 covers all of the cases that > you > > identify below. Tnx. > > Maybe I overlooked

Re: [sqlite] [patch][rebase for 3.8.2] really move "const" check out of loop "WHERE const" (and "WHERE const AND expr" optimization)

Richard Hipp wrote: > On Thu, Jan 2, 2014 at 3:25 PM, Yuriy Kaminskiy wrote: > >> Richard Hipp wrote: >>> Please verify that the alternative optimization checked-in at >>> http://www.sqlite.org/src/info/b7e39851a7 covers all of the cases that >>> you identify below. Tnx. >>