Re: [sqlite] Python - database disk image is malformed

On 07/09/14 19:11, Andres Riancho wrote: > * I'm setting [4] "PRAGMA synchronous=OFF" for increased > performance. Can this trigger malformed errors? Read the doc: https://sqlite.org/pragma.html#pragma_synchronous TLDR: yes To improve write performance use WAL:

Re: [sqlite] Python - database disk image is malformed

On 8 Sep 2014, at 3:11am, Andres Riancho wrote: >I'm using sqlite as the database backend for an open source > project and it works perfectly 99% of the time; however some users > have reported "database disk image is malformed" errors [1][2]. There are two

[sqlite] Python - database disk image is malformed

List, I'm using sqlite as the database backend for an open source project and it works perfectly 99% of the time; however some users have reported "database disk image is malformed" errors [1][2]. At the moment the w3af project has a really clean wrapper around sqlite [3] which allows

Re: [sqlite] Transactions for read operations

Thanks to those who responded to my query. Simon: It will be easier to code if every page commits, regardless of whether any write operations occurred (and rollback only error) - so your answer pleased me greatly. Keith: Yes, you're right. I'm not passing a single database connection around,

Re: [sqlite] Request to change int parameter to size_t parameter / potential bug on iOS (64 bit)

Am 07.09.2014 um 21:52 schrieb Simon Slavin : > > On 7 Sep 2014, at 7:19pm, Richard Hipp wrote: > >> mailingli...@skywind.eu> wrote: >> >>> Is it possible to change the fourth parameter in sqlite3_bind_XXX (and >>> probably other locations) because this

[sqlite] Query help

I have a query I am trying to rewrite as efficient as possible and not clear. SELECT x.id, x.col FROM table_a x EXCEPT SELECT y.id, y.col FROM table_b y JOIN table_a . The right hand part of the except performs several joins and already duplicates the entire query on the left hand

Re: [sqlite] Request to change int parameter to size_t parameter / potential bug on iOS (64 bit)

On 7 Sep 2014, at 7:19pm, Richard Hipp wrote: > mailingli...@skywind.eu> wrote: > >> Is it possible to change the fourth parameter in sqlite3_bind_XXX (and >> probably other locations) because this seems to be for me the appropriate >> type?! > > No. That would be a

Re: [sqlite] Can't figure out how to report a bug

Words aren't big enough on that page. I was expecting to find a link where things are posted. It was a case of TL;DR. > > From: Roger Binns >To: Joe Mucchiello ; General Discussion of SQLite >Database

Re: [sqlite] SQLITE_THREADSAFE question

On 04/09/14 06:59, Neo Anderson wrote: > I'm building a custom library wrapper for Cocoa. I want to handle database > threading issue myself. One gotcha not documented in the threading pages is that the SQLite error handling APIs are not threadsafe, and the only correct way of handling errors

Re: [sqlite] Request to change int parameter to size_t parameter / potential bug on iOS (64 bit)

On 07/09/14 11:19, Richard Hipp wrote: > Please use a cast to silence the compiler warnings. "(int)sizeof(...)" > instead of just "sizeof(...)". That isn't safe for correctly written 64 bit apps. For example they could end up with data items that are bigger than 2GB correctly using (s)size_t.

Re: [sqlite] Request to change int parameter to size_t parameter / potential bug on iOS (64 bit)

On 07/09/14 10:02, skywind mailing lists wrote: > I have seen that SQLite uses normally parameters of type "int" to pass the > size of a variable Correct. It should be using size_t or ssize_t, but the SQLite developers chose not to do that, especially as at the time of the decision those

Re: [sqlite] Does the Connection string support UNC paths?

Thanks for the info. I was unaware of the forum. I've registered there now as well. -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Kevin Benson Sent: Sunday, September 07, 2014 1:43 AM To: General Discussion of SQLite

Re: [sqlite] Request to change int parameter to size_t parameter / potential bug on iOS (64 bit)

On Sun, Sep 7, 2014 at 1:02 PM, skywind mailing lists < mailingli...@skywind.eu> wrote: > > Is it possible to change the fourth parameter in sqlite3_bind_XXX (and > probably other locations) because this seems to be for me the appropriate > type?! > No. That would be a compatibility break.

Re: [sqlite] Request to change int parameter to size_t parameter / potential bug on iOS (64 bit)

On Sun, Sep 7, 2014 at 8:08 PM, Stephen Chrzanowski wrote: > On Sun, Sep 7, 2014 at 1:02 PM, skywind mailing lists < > mailingli...@skywind.eu> wrote:> type?! On iOS 64bit the size of int is 4 > bytes and the size of size_t is 8 > > bytes. In this case the fourth parameter

Re: [sqlite] Can't figure out how to report a bug

On 07/09/14 05:20, Joe Mucchiello wrote: > So I'm posting it here. For the record, this wiki page explains how to report a SQLite bug (first google result too): https://www.sqlite.org/src/wiki?name=Bug+Reports Your issue is covered in the FAQ. Roger

Re: [sqlite] Request to change int parameter to size_t parameter / potential bug on iOS (64 bit)

Wouldn't it come down to the compiler you're using that'd indicate the number of bytes associated to an integer type, or at least tell the compiler to compile integer types to 64-bit? On Sun, Sep 7, 2014 at 1:02 PM, skywind mailing lists < mailingli...@skywind.eu> wrote: > Hello, > > I have

Re: [sqlite] Can't figure out how to report a bug

On 2014-09-07, 8:26 AM, Joe Mucchiello wrote: PmaReader *pReadr; SortSubtask *pLast = >aTask[pSorter->nTask-1]; rc = vdbeSortAllocUnpacked(pLast); if( rc==SQLITE_OK ){ pReadr = (PmaReader*)sqlite3DbMallocZero(db, sizeof(PmaReader)); pSorter->pReader

Re: [sqlite] Can't figure out how to report a bug

On 7 Sep 2014, at 5:34pm, Joe Mucchiello wrote: > Sorry, but if VS13 is a supported compiler. Actually I don't know what 'supported compiler' means for SQLite. I'm not even sure specific compilers are supported. I think any appeal would have to be made referring to

[sqlite] Request to change int parameter to size_t parameter / potential bug on iOS (64 bit)

Hello, I have seen that SQLite uses normally parameters of type "int" to pass the size of a variable (see sqlite3_bind_blob, fourth parameter). When compiling SQLite3 with Clang and some warnings enabled I get warnings when passing sizeof(...) as the fourth parameter. The reason is that

Re: [sqlite] Can't figure out how to report a bug

Joe Mucchiello wrote: > if VS13 is a supported compiler. Then whatever it reports as an error > should be fixed. This is not an error but a warning. You have set a compiler option to treat all warnings as errors. Remove it. > It does not hurt to initialize the variable since I'm sure those

Re: [sqlite] Can't figure out how to report a bug

Sorry, but if VS13 is a supported compiler. Then whatever it reports as an error should be fixed. Not everyone who grabs the amalgam file to compile it can figure out how to "fix" compiler errors. Are you saying it is not worth suppressing this error just because it's only in one compiler?

Re: [sqlite] pls dont send so many message - once a month is enough

Rafi, From looking at your email address, it would seem to me that you are likely not a native English speaker. Which makes your Subject more amusing that upsetting. Why would it be upsetting? Because it comes across as a person walking into a community center and complaining that the sound level

Re: [sqlite] Can't figure out how to report a bug

This is the right way to report a bug, and as soon as you encounter a bug, you should report it here. As for the current query, this is not a bug, it's a VS13 compiler peculiarity which they feel pertinent to report on, but which does not affect the ability of SQLite to produce the correct

[sqlite] Can't figure out how to report a bug

So I'm posting it here. The 3.8.6 Amalgam file generates an error in VS13 on Windows: sqlite3.c(77874): error C4703: potentially uninitialized local pointer variable 'pReadr' used This is from the source file src/vbesort.c in a function called vdbeSorterSetupMerge: PmaReader *pReadr;

[sqlite] Can't figure out how to report a bug

So I'm posting it here. The 3.8.6 Amalgam file generates an error in VS13 on Windows: ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Does the Connection string support UNC paths?

> > Mensaje original > De: "Chris" > Para: > Fecha: Sat, 6 Sep 2014 23:46:19 -0500 > Asunto: [sqlite] Does the Connection string support UNC paths? > > > >I am old database programmer that just came across SQLite and am working

[sqlite] pls dont send so many message - once a month is enough

-- בברכה, רפי טוביה 2570401 052 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Does the Connection string support UNC paths?

On Sun, Sep 7, 2014 at 12:46 AM, Chris wrote: > I am old database programmer that just came across SQLite and am working on > a small project for a PVR that uses SQLite as it's db provider. I try > specifying a UNC path to the database for the datasource in the