[sqlite] Sqlite connection/ Sqlite3_open

On 5 Oct 2015, at 11:02pm, Steave Njinwoua wrote: > I would like to use this knowledge for managing > sqlite db. AS anyone ever faces the same problem or can someone help ? > Thanks in advance. Split the problem into two. 1) Learn SQL syntax and test your knowledge. 2) Learn how to use C# to e

[sqlite] SQLITE_BUSY_SNAPSHOT from BEGIN IMMEDIATE

* Rowan Worth: > On 29 September 2015 at 03:47, Florian Weimer wrote: > >> Relatively rarely, while starting a transaction on a concurrently >> modified SQLite database in WAL mode, I get a SQLITE_BUSY_SNAPSHOT >> error for just-prepared "BEGIN IMMEDIATE" statement. >> > > BEGIN IMMEDIATE takes a

[sqlite] What's the status of SQLite4? Where can I find its source code?

There was a flurry of postings on HackerNews about SQLite4 that made it seem like it might be arriving soon, and people might have got excited and heard about it that way, I know I did. On Mon, Oct 5, 2015 at 9:47 AM, Scott Robison wrote: > It seems to me the reason these questions keep coming u

[sqlite] in memory database bug or documentation mismatch

@Richard Hipp No i did not enable URI interpolattion,.., i will try with sqlite3_openv2... Thanks, will let you know if it worked out On Mon, Oct 5, 2015 at 2:30 PM, Richard Hipp wrote: > On 10/5/15, Jacob wrote: >> Hello, >> >> I have tried to create an in memory database according to the >>

[sqlite] in memory database bug or documentation mismatch

@Stephen Chrzanowski p Its a verbatim quote from the documentation, so its legal. On Mon, Oct 5, 2015 at 3:22 PM, Stephen Chrzanowski wrote: > I'm not familiar with this method, but, shouldn't it be file::memory: or > something of the sort? > > On Mon, Oct 5, 2015 at 8:30 AM, Richard Hipp wrot

[sqlite] Performance issue with CTE

Just to let you know, the solution using SELECT * FROM (query with offset/limit) works perfectly well. Thanks a lot for the suggestion!

[sqlite] Incorrect limit behavior in conjunction with offset, union all, and order by.

The following SQL outputs more rows than expected. The behavior seems to require the use of UNION ALL, ORDER BY (in the column being selected), and an OFFSET. Swapping the two clauses of the union also produces the wrong result, though it's definitely necessary to order by x. The answer is also

[sqlite] How do i submit a bug?

On 5 Oct 2015, at 2:13pm, Simon Davies wrote: > Was the library compiled with "SQLITE_USE_URI=1"? > (See "Backwards Compatibility" in https://www.sqlite.org/uri.html) You can find out using PRAGMA compile_options Simon.

[sqlite] How do i submit a bug?

On 5 October 2015 at 10:48, Jacob wrote: > Hi John, > > I have tried to create an in memory database according to the > documentation on this link > https://www.sqlite.org/inmemorydb.html > > The documentation lists: (C code) > > rc = sqlite3_open("file:memdb1?mode=memory&cache=shared", &db); > >

[sqlite] sqlite-users Digest, Vol 94, Issue 4

> > Ok. My first guess is that you are missing the "suggested index" on the > child table. Without this, if there is a foreign key violation in the > db, each insert on the parent table will cause a linear scan of the > entire child table. With the index, it's just a simple seek. > > https://www.sq

[sqlite] How do i submit a bug?

Hi John, I have tried to create an in memory database according to the documentation on this link https://www.sqlite.org/inmemorydb.html The documentation lists: (C code) rc = sqlite3_open("file:memdb1?mode=memory&cache=shared", &db); It creates a file on disk this is not supposed to happen

[sqlite] in memory database bug or documentation mismatch

Hello, I have tried to create an in memory database according to the documentation on this link https://www.sqlite.org/inmemorydb.html The documentation lists: (C code) rc = sqlite3_open("file:memdb1?mode=memory&cache=shared", &db); It creates a file on disk this is not supposed to happen.

[sqlite] SQLITE_CANTOPEN after days of operation

Hi I have a strange issue with a piece of C code using sqlite3. The code runs for days and then stops on an SQL insert into db with the error code SQLITE_CANTOPEN. Further info: 1) The program is a status monitoring app - it writes values into the SQL db once every 60 seconds. Average duration

[sqlite] in memory database bug or documentation mismatch

I'm not familiar with this method, but, shouldn't it be file::memory: or something of the sort? On Mon, Oct 5, 2015 at 8:30 AM, Richard Hipp wrote: > On 10/5/15, Jacob wrote: > > Hello, > > > > I have tried to create an in memory database according to the > > documentation on this link > > http

[sqlite] What's the status of SQLite4? Where can I find its source code?

It seems to me the reason these questions keep coming up because people are encouraged to use the latest and greatest version of SQLite 3 at all times, and SQLite 4 sounds like something even later and greater. I wonder if a name like SQLite X might reduce the number of queries. Well, maybe not SQL

[sqlite] in memory database bug or documentation mismatch

On 10/5/15, Jacob wrote: > Hello, > > I have tried to create an in memory database according to the > documentation on this link > https://www.sqlite.org/inmemorydb.html > > The documentation lists: (C code) > > rc = sqlite3_open("file:memdb1?mode=memory&cache=shared", &db); Did you enable URI fi

[sqlite] What's the status of SQLite4? Where can I find its source code?

I simply noticed others inquiring about sqlite4. As I am doing a new project, if it was going to be available in the near future then I would start playing with it and use its features. But if it will be years, and is mostly a play ground, then it is not an issue to ponder for now.. --

[sqlite] SQLITE_CANTOPEN after days of operation

On 10/5/15, Andrew Miles wrote: > Hi > > I have a strange issue with a piece of C code using sqlite3. The code runs > for days and then stops on an SQL insert into db with the error code > SQLITE_CANTOPEN. > > Further info: > > 1) The program is a status monitoring app - it writes values into the

[sqlite] What's the status of SQLite4? Where can I find its source code?

Jerry & Scott: What are you hoping to achieve with SQLite4 that you cannot do with SQLite3? On 10/5/15, Stephen Chrzanowski wrote: > There was a thread sometime last year about this. Basically, SQLite4 isn't > planned for a release at this time, and from what I understood then, > chances are th

[sqlite] How do i submit a bug?

On 2015-10-05 12:22 AM, Jacob wrote: > Hi, I have discovered a bug, or at least inconsistancy with documantation, > > DO i submit the bug through this mailing list, or is there a ticket system? This is the place to post it. Some of the people here will look into it and if it is found to be a bu

[sqlite] What's the status of SQLite4? Where can I find its source code?

There was a thread sometime last year about this. Basically, SQLite4 isn't planned for a release at this time, and from what I understood then, chances are there isn't going to be a thought towards release for at few more years. It basically is a playground to test theories, it is buggy, and such

[sqlite] How do i submit a bug?

Hi, I have discovered a bug, or at least inconsistancy with documantation, DO i submit the bug through this mailing list, or is there a ticket system? Regards Jacob

[sqlite] What's the status of SQLite4? Where can I find its source code?

https://sqlite.org/src4/tree?ci=trunk On Mon, Oct 5, 2015 at 12:02 AM, Jerry wrote: > Seems I could not find its source code ... > https://sqlite.org/src4/doc/trunk/www/index.wiki > > Thanks. > ___ > sqlite-users mailing list > sqlite-users at mailingl