Re: [sqlite] Write-ahead logging issue on Android

On Fri, Oct 4, 2013 at 2:55 PM, Sascha Sertel wrote: > > I'm working on a multi-platform app that uses a cross-platform library with > SQLite 3.7.16.1 built into it (i.e. not using the built-in SQLite version > in Android or other platforms). We make (re)use of prepared

Re: [sqlite] Write-ahead logging issue on Android

On 4 Oct 2013, at 10:26pm, Sascha Sertel wrote: > The error does not come up immediately, creating tables works fine, making > inserts works fine, it's only when I start making updates (from multiple > threads) where this error starts showing up. Any chance that the

Re: [sqlite] Write-ahead logging issue on Android

I can see the .wal and .shm files getting created and don't see a reason why SQLite would suddenly have issues accessing those files. The error does not come up immediately, creating tables works fine, making inserts works fine, it's only when I start making updates (from multiple threads) where

Re: [sqlite] Write-ahead logging issue on Android

On 10/05/2013 01:55 AM, Sascha Sertel wrote: Hello everybody, I'm hoping someone might have some insights on a particular issue I've been running into. Here some details: I'm working on a multi-platform app that uses a cross-platform library with SQLite 3.7.16.1 built into it (i.e. not using

Re: [sqlite] Virtual Table: misuse error on sqlite3_declare_vtab()

GOT IT. Well, I found my mistake that lead to all this. I'm sorry to have wasted your time. Here's what happened for those who struggle with similar issues... I originally opted to make sqlite3_module a member of my C++ "module" class. My C++ constructor was therefore assigning all the

Re: [sqlite] Virtual Table: misuse error on sqlite3_declare_vtab()

The option was already on for my own stuff but not sqlite. However, I just had to recompile libSqlite3 with debug option to get more details and it's a bit scary... SQL query using sqlite3_exec() and stmt: create virtual table foo using vtable_module1; -Calling sqlite3_prepare_v2()... -Calling

[sqlite] Write-ahead logging issue on Android

Hello everybody, I'm hoping someone might have some insights on a particular issue I've been running into. Here some details: I'm working on a multi-platform app that uses a cross-platform library with SQLite 3.7.16.1 built into it (i.e. not using the built-in SQLite version in Android or other

Re: [sqlite] 3.8.1

On 10/4/2013 12:32, Peter Haworth wrote: I've seen emntion of version 3.8.1 of sqlite - is there a document somwhere that describes the changes? https://www.sqlite.org/draft/releaselog/current.html You could have found that link yourself from the SQLite download page, right next to the link

Re: [sqlite] 3.8.1

On Fri, Oct 4, 2013 at 2:32 PM, Peter Haworth wrote: > I've seen emntion of version 3.8.1 of sqlite - is there a document somwhere > that describes the changes? > http://www.sqlite.org/draft/releaselog/current.html -- D. Richard Hipp d...@sqlite.org

[sqlite] 3.8.1

I've seen emntion of version 3.8.1 of sqlite - is there a document somwhere that describes the changes? Thanks, Pete lcSQL Software ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] Virtual Table: misuse error on sqlite3_declare_vtab()

On Fri, Oct 4, 2013 at 2:22 PM, Simon wrote: > Hi Richard, > > That helped a lot and got me passed that point. However, I didn't go very > far from where I were... > > It now compiles fine, however the program segfaults within the > sqlite3_step() of the "create virtual

Re: [sqlite] Virtual Table: misuse error on sqlite3_declare_vtab()

Hi Richard, That helped a lot and got me passed that point. However, I didn't go very far from where I were... It now compiles fine, however the program segfaults within the sqlite3_step() of the "create virtual table foo using vtable_module1;" statement. Using valgrind, I get this interesting

Re: [sqlite] Major performance difference when joining on FTS4 table's docid column versus custom id column

I ended up going with an external content table, and now everything works like a charm with the expected level of performance. Thanks for the help! -Per On Thu, Oct 3, 2013 at 6:46 AM, Clemens Ladisch wrote: > Per Vognsen wrote: > > Am I wrong to think that joining on

Re: [sqlite] Virtual Table: misuse error on sqlite3_declare_vtab()

On Fri, Oct 4, 2013 at 10:07 AM, Simon wrote: > > 3) I call sqlite3_create_module() with module name "vtable1" > > 4) I call sqlite3_declare_vtab() with this statement: "CREATE TABLE foo ( x > integer, y integer );" > The application must never invoke

Re: [sqlite] Virtual Table: misuse error on sqlite3_declare_vtab()

Simon, don't know what exactly wrong in your particular case, but I'd suggest setting debugger breakpoints everywhere in your x-handlers and notice the moment after which calls are ceased (or you get a error code). Max On Fri, Oct 4, 2013 at 6:07 PM, Simon wrote: > Hi

[sqlite] Virtual Table: misuse error on sqlite3_declare_vtab()

Hi there, I'm currently building my own virtual table implementation. I've built a dummy vtable that returns the string "1" to all queries for all columns but I'm having trouble getting started (getting a 'misuse' error). Can someone help me get in the right direction? > 1) I

Re: [sqlite] Array Accessing in SQLite

On 4 Oct 2013, at 9:32am, techi eth wrote: > Can anyone let me know what is best way to handle C Array in SQLite3 database > ? > > As of now I can think of creating multiple row for storing each array > element. When you need the contents of one of the elements of the

[sqlite] Array Accessing in SQLite

Hi, Can anyone let me know what is best way to handle C Array in SQLite3 database ? As of now I can think of creating multiple row for storing each array element. Thanks.. ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] SQLite4 release date and how to compile on windows platform

On 4 Oct 2013, at 6:44am, Zarian Waheed wrote: > Does anyone know if any release date has been announced for SQLite4? We do know that it hasn't. > Secondly where can I find the instructions to compile SQLite4 on windows > platform. The instructions aren't that