Re: [sqlite] basic "Window function"

On 2014-03-13, 8:17 AM, big stone wrote: Hello again, Windowing functions are : - not easy to workaround with create_function(), - a truly "sql core" motor functionality. The only use case that I have, is the small subset I described earlier : - inside one 'select' : . several

[sqlite] failure to build static library with -DSQLITE_ENABLE_ICU

Hello, I have been trying to build sqlite 3.8.4.1 using the ICU extension and have seem to have hit an apparent bug in the sqlite code. After much debugging, it looks like the header is missing, which causes warnings like the following to appear: sqlite3.c: In function 'icuLikeCompare':

Re: [sqlite] [sqlite-dev] Final preparations for the release of System.Data.SQLite v1.0.92.0 have begun...

Stefano Ravagni wrote: > > Only SQL Server don't follow this line for what i know, and because of > that i abandon it in favor of SQlite (as file system database) and > PostgreSQL. > Well, the SQL Server provider is included with the .NET Framework itself and I assume that they know how to

Re: [sqlite] Reader locks writer in truncate mode?

On 13 Mar 2014, at 11:12pm, veeresh kumar wrote: > Thanks a lot for the response. Is there any way to identify which > thread/process is actually blocking the reader thread or vise versa? Only in that it's the one that didn't get the error message. The one that's in the

Re: [sqlite] Reader locks writer in truncate mode?

Thanks a lot for the response. Is there any way to identify which thread/process is actually blocking the reader thread or vise versa?   -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Simon Slavin Sent: Thursday, March 13,

Re: [sqlite] Reader locks writer in truncate mode?

On 3/13/2014 5:24 PM, veeresh kumar wrote: In a multi-threaded application, say a reader thread has read 100 records from the table and reading is still in progress before which writer thread writes data and tries to commit. Its causing database lock.Is this expected? Assuming the two

[sqlite] Reader locks writer in truncate mode?

In a multi-threaded application, say a reader thread has read 100 records from the table and reading is still in progress before which writer thread writes data and tries to commit. Its causing database lock.Is this expected? Note : journal_mode is set as truncate

Re: [sqlite] Reader locks writer in truncate mode?

On 13 Mar 2014, at 9:27pm, Igor Tandetnik wrote: > On 3/13/2014 5:24 PM, veeresh kumar wrote: >> In a multi-threaded application, say a reader thread has read 100 records >> from the table and reading is still in progress before which writer thread >> writes data and tries

Re: [sqlite] [sqlite-dev] Final preparations for the release of System.Data.SQLite v1.0.92.0 have begun...

Stefano Ravagni wrote: > > Yes, i think tue value have to remain constant as far as i explicit close datareader. > This have an important effect; possibility to valle a datareader in a specific routine > and obtain hasrows value out of this routine. > The MSDN docs are unclear on this point;

Re: [sqlite] Crash if "sqlite3_db_release_memory" has no memory to release

On Thu, Mar 13, 2014 at 2:57 PM, Eduardo Morras wrote: > > Hi, I get app crash if sqlite3_db_release_memory(db) is called and Sqlite3 > has no memory to release, for example calling it twice. > > The backtrace is: > > #0 0x0042ab60 in sqlite3PcacheShrink

Re: [sqlite] which of these is faster?

On Thu, Mar 13, 2014 at 2:37 PM, Stephan Beal wrote: > Hi, all, > > i know this is probably splitting hairs, and i ask only out of curiosity, > not because i'm looking to optimize at this level... > > Given a Fossil repository db (namely the event.mtime value, a Julian

[sqlite] Crash if "sqlite3_db_release_memory" has no memory to release

Hi, I get app crash if sqlite3_db_release_memory(db) is called and Sqlite3 has no memory to release, for example calling it twice. The backtrace is: #0 0x0042ab60 in sqlite3PcacheShrink (pCache=0x6f6c6f63207b2065) at /usr/home/gowen/clang/scgi/src/sqlite3.c:37835 #1

Re: [sqlite] which of these is faster?

On Thu, Mar 13, 2014 at 7:50 PM, Andreas Kupries wrote: > WIBNI regardless of which form is faster, the engine would detect and > rewrite the slower into the other ? > i wouldn't quite expect the engine to figure that out, but of course would be happy if it could. >

Re: [sqlite] which of these is faster?

On Thu, Mar 13, 2014 at 11:37 AM, Stephan Beal wrote: > Hi, all, > > i know this is probably splitting hairs, and i ask only out of curiosity, > not because i'm looking to optimize at this level... > > Given a Fossil repository db (namely the event.mtime value, a Julian

[sqlite] which of these is faster?

Hi, all, i know this is probably splitting hairs, and i ask only out of curiosity, not because i'm looking to optimize at this level... Given a Fossil repository db (namely the event.mtime value, a Julian Day), which of the following is faster for finding the min/max value of that field: SELECT

Re: [sqlite] basic "Window function"

On 2014/03/13 20:02, Petite Abeille wrote: On Mar 13, 2014, at 4:17 PM, big stone wrote: Is there anyone else, (besides little bee), that would "like" this request? "Oh! Oh pick me! Pick me! Me! Me! M!” — Donkey, Shrek Hehe, I live in a Country with 11 official

Re: [sqlite] basic "Window function"

On Mar 13, 2014, at 4:17 PM, big stone wrote: > Is there anyone else, (besides little bee), that would "like" this request? "Oh! Oh pick me! Pick me! Me! Me! M!” — Donkey, Shrek ___ sqlite-users mailing list

Re: [sqlite] basic "Window function"

Hello again, Windowing functions are : - not easy to workaround with create_function(), - a truly "sql core" motor functionality. The only use case that I have, is the small subset I described earlier : - inside one 'select' : . several sum/min/avg/max (different fields) , . all with

Re: [sqlite] sqlite3_progress_handler callback behavior change

Hi, > On 13 Mar 2014, at 13:21, big stone wrote: > Does it mean we may have SQLite3.8.4.1 in imminent Python 3.4 release ? > > http://bugs.python.org/issue20901 This question did come up when building/packaging that and other versions of Python with SQLite 3.8.4(.1),

Re: [sqlite] sqlite3_progress_handler callback behavior change

Hello Andreas, Does it mean we may have SQLite3.8.4.1 in imminent Python 3.4 release ? http://bugs.python.org/issue20901 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Problem with sqlite3_exec

On 3/13/2014 6:33 AM, khaloud1987 wrote: I have a problem with sqlite3_exec that the first delete execute suuccesfully but the second delete (table2) does not. My qustion is : sqlite_exec can return a value different with SQLITE_OK and it works ok What value does the second call return?

Re: [sqlite] sqlite3_progress_handler callback behavior change

On Wed, Mar 12, 2014 at 5:27 PM, Andreas Stieger wrote: > Hello, > > I noticed a change in behavior of sqlite3_progress_handler for CREATE > TABLE, or rather the calls to the callbacks, and just wanted to get > clarification if this was intentional. > > Specifically, given

Re: [sqlite] [sqlite-dev] Final preparations for the release of System.Data.SQLite v1.0.92.0 have begun...

i encounter problem with datareader hasrows properties... After data association the property became FALSE also if data is present Is not good thing for who use datareader.hasrows for check data presence... Is possible to fix this problem ? Il giorno martedì 11 marzo 2014 02:22:31 UTC+1,

[sqlite] sqlite3_progress_handler callback behavior change

Hello, I noticed a change in behavior of sqlite3_progress_handler for CREATE TABLE, or rather the calls to the callbacks, and just wanted to get clarification if this was intentional. Specifically, given the code below for a callback that prints one "." for each code for this: (full code below)

[sqlite] Problem with sqlite3_exec

Hello, I have a problem with sqlite3_exec that the first delete execute suuccesfully but the second delete (table2) does not. My qustion is : sqlite_exec can return a value different with SQLITE_OK and it works ok this is my code: snprintf(query,q_size,"DELETE FROM " table1 " where

[sqlite] Datareader HasRows became empty after binding source

Hello, i'm a .NET developer and i'm trying to use Sqlite as connector. I could see in an instruction as If Dati.HasRows = True Then sorgente.DataSource = Dati end if where DATI is a datareader object and SORGENTE is a BINDINGSOURCE object, after association with from datareader