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

Thanks Gabriel. That answers my question. Thanks, Zarian. Sent from Yahoo! Mail on Android ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Inserting or replacing in the same db based on one key

On Wed, 9 Oct 2013 17:00:36 -0400 "jose isaias cabrera" wrote: > CREATE TABLE SimplePrices ( > cust TEXT, > class TEXT, > slang TEXT, > tlang TEXT, > TransferCost, > Price, > PRIMARY

[sqlite] Inserting or replacing in the same db based on one key

Greetings. I have this table creation code, CREATE TABLE SimplePrices ( cust TEXT, class TEXT, slang TEXT, tlang TEXT, TransferCost, Price, PRIMARY KEY (cust, class, slang, tlang)); and I have lots of data

Re: [sqlite] Bug: analyze.c does not honor SQLITE_64BIT_STATS

On Wed, Oct 9, 2013 at 9:49 PM, James K. Lowden wrote: > > It's difficult to do portably because you have to account for every > combination of standard C library and integer size > Remember that SQLite does not use the standard library printf() function. It has its

Re: [sqlite] Bug: analyze.c does not honor SQLITE_64BIT_STATS

On Wed, 09 Oct 2013 10:20:13 -0400 Ryan Johnson wrote: > > This is more portable: > > > > #ifdef SQLITE_64BIT_STATS > > sqlite3_snprintf(24, zRet, "%lld", p->nRow); > > #else > > sqlite3_snprintf(24, zRet, "%d", p->nRow); > > #endif > Actually,

Re: [sqlite] COMMIT in SQLite

Thanks guys. Perhaps docs could be updated in the _prepare_v2 section, to mention the 'best practices' lifecycle of a statement in regards to commit On 9 October 2013 04:08, Stephan Beal wrote: > On Tue, Oct 8, 2013 at 9:58 PM, Petite Abeille

Re: [sqlite] getting more context on SQL parse errors

I second that. Staffan On Tue, Oct 8, 2013 at 7:25 PM, Nelson, Erik - 2 < erik.l.nel...@bankofamerica.com> wrote: > When a SQL parsing error happens, the message returned by sqlite3_errmsg() > is pretty terse... is there some way to retrieve more context, so that the > user has more than one

Re: [sqlite] Easy way to change a column

On Oct 9, 2013, at 2:50 AM, Bao Niu wrote: > For SQLite is there an easy way to find out ALL other tables, queries and > triggers that will be affected when performing a change to a particular > column under the cursor? No. > That would make refactoring so much easier.

Re: [sqlite] Bug: analyze.c does not honor SQLITE_64BIT_STATS

On 09/10/2013 10:07 AM, Ralf Junker wrote: On 09.10.2013 15:50, Eric Minbiole wrote: With this change, tests pass again: #if sizeof(p->nRow) == sizeof(long long) sqlite3_snprintf(24, zRet, "%lld", p->nRow); #elseif sizeof(p->Row) = sizeof(long) sqlite3_snprintf(24, zRet,

Re: [sqlite] Bug: analyze.c does not honor SQLITE_64BIT_STATS

On 09.10.2013 15:50, Eric Minbiole wrote: With this change, tests pass again: #if sizeof(p->nRow) == sizeof(long long) sqlite3_snprintf(24, zRet, "%lld", p->nRow); #elseif sizeof(p->Row) = sizeof(long) sqlite3_snprintf(24, zRet, "%ld", p->nRow); #else

Re: [sqlite] Bug: analyze.c does not honor SQLITE_64BIT_STATS

On 10/9/2013 9:50 AM, Eric Minbiole wrote: With this change, tests pass again: #if sizeof(p->nRow) == sizeof(long long) sqlite3_snprintf(24, zRet, "%lld", p->nRow); #elseif sizeof(p->Row) = sizeof(long) sqlite3_snprintf(24, zRet, "%ld", p->nRow); #else

Re: [sqlite] Bug: analyze.c does not honor SQLITE_64BIT_STATS

> With this change, tests pass again: > > #if sizeof(p->nRow) == sizeof(long long) > sqlite3_snprintf(24, zRet, "%lld", p->nRow); > #elseif sizeof(p->Row) = sizeof(long) > sqlite3_snprintf(24, zRet, "%ld", p->nRow); > #else > sqlite3_snprintf(24, zRet, "%d", p->nRow); >

[sqlite] Bug: analyze.c does not honor SQLITE_64BIT_STATS

analyze.c always prints 32-bit variables as 64-bit here: http://www.sqlite.org/src/artifact/d322972af09e3f8debb45f420dfe3ded142b108b?ln=746 http://www.sqlite.org/src/artifact/d322972af09e3f8debb45f420dfe3ded142b108b?ln=792 This can cause wrong sqlite_statX tables which I have experienced