[sqlite] keep out focus

2016-03-22 Thread hfiandor
Dear sirs: I want to appology for this message. Initially I want to send to the Lazarus List, but if anyone has the solution, I will appreciate very much Thanks Yours Ing. H?ctor F. Fiandor Rosario

[sqlite] Article about pointer abuse in SQLite

2016-03-22 Thread Donald Shepherd
On Wed, 23 Mar 2016 12:59 am Adam Devita wrote: > > This discussion on the nature of undefined behaviour code is > interesting. I don't know the reasoning, but it seems that VS6 often > initialized things to 0xcd in debug mode and (usually) had memory > uninitialized to 0x00 when complied in

[sqlite] Article about pointer abuse in SQLite

2016-03-22 Thread James K. Lowden
On Tue, 22 Mar 2016 11:00:24 -0500 "Marc L. Allen" wrote: > I don't think compilers "run" your code. Provided we're talking about a C compiler, you're right. Optimizers don't run the code, they reason about it. > The fact that the code never actually allows that path to occur is > beyond

[sqlite] Article about pointer abuse in SQLite

2016-03-22 Thread James K. Lowden
On Tue, 22 Mar 2016 09:58:52 -0400 Adam Devita wrote: > I don't know the reasoning, but it seems that VS6 often > initialized things to 0xcd in debug mode and (usually) had memory > uninitialized to 0x00 when complied in Release (perhaps 0x00 just > happens to be what was on the stack or heap).

[sqlite] Article about pointer abuse in SQLite

2016-03-22 Thread James K. Lowden
On Tue, 22 Mar 2016 09:56:57 +0100 "Cezary H. Noweta" wrote: > On 2016-03-22 00:35, James K. Lowden wrote: > >[...] An example from Clang's discussion is > > > > int i = 10 << 31; > > Could you provide a link for that discussion? (Or google's phrase to > retrieve such link?) I'm sorry,

[sqlite] Article about pointer abuse in SQLite

2016-03-22 Thread Keith Medcalf
> This discussion on the nature of undefined behaviour code is > interesting. I don't know the reasoning, but it seems that VS6 often > initialized things to 0xcd in debug mode and (usually) had memory > uninitialized to 0x00 when complied in Release (perhaps 0x00 just > happens to be what was

[sqlite] FTS5 "constraint failed"

2016-03-22 Thread Domingo Alvarez Duarte
Hello ! It's a sqlite repository clone that follows trunk. SQLite version 3.12.0 2016-03-22 15:26:03 Enter ".help" for usage hints Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. Cheers ! ? > Tue Mar 22 2016 06:23:53 PM CET from

[sqlite] FTS5 "constraint failed"

2016-03-22 Thread Domingo Alvarez Duarte
In this case sqlite is compiled with the following flags: gcc -g -O2 -DSQLITE_OS_UNIX=1 -I. -I/third-party/sqlite3/src -I/third-party/sqlite3/ext/rtree -I/third-party/sqlite3/ext/fts3 -D_HAVE_SQLITE_CONFIG_H -DBUILD_sqlite -DSQLITE_HAS_CODEC=1 -DSQLITE_ENABLE_FTS4=1 -DSQLITE_ENABLE_FTS3

[sqlite] FTS5 "constraint failed"

2016-03-22 Thread Domingo Alvarez Duarte
Hello ! After seeing several times work/commits on fts5 I decided to try it on a table shown bellow, and when trying to populate it I get this error message: sqlite> INSERT INTO fts_idx_items(fts_idx_items) VALUES('rebuild'); Error: constraint failed The table has 12,000,000 records and

[sqlite] Version 3.12.0 coming soon

2016-03-22 Thread Simon Slavin
On 22 Mar 2016, at 4:42pm, Richard Hipp wrote: > A preview of the change log can be seen at > https://www.sqlite.org/draft/releaselog/3_12_0.html " ? The query planner considers the LIMIT clause when estimating the cost or ORDER BY. ? The configure script (on unix) automatically

[sqlite] sqldiff nowadays

2016-03-22 Thread Alek Paunov
On 2016-03-22 13:49, Richard Hipp wrote: > On 3/22/16, MM wrote: >> Hello, >> I can see sqldiff appearing here: >> >> https://www.sqlite.org/sqldiff.html >> >> and in the downloads page as part of a linux 32bit binary package. >> Alas I don't see any 64bit package. > > The 32bit binaries will run

[sqlite] sqldiff nowadays

2016-03-22 Thread MM
On 22 March 2016 at 13:28, Alek Paunov wrote: > On 2016-03-22 13:49, Richard Hipp wrote: > >> On 3/22/16, MM wrote: >> >>> Hello, >>> I can see sqldiff appearing here: >>> >>> https://www.sqlite.org/sqldiff.html >>> >>> and in the downloads page as part of a linux 32bit binary package. >>> Alas

[sqlite] sqldiff nowadays

2016-03-22 Thread Matthias-Christian Ott
On 22/03/16 11:49, Richard Hipp wrote: > On 3/22/16, MM wrote: >> Hello, >> I can see sqldiff appearing here: >> >> https://www.sqlite.org/sqldiff.html >> >> and in the downloads page as part of a linux 32bit binary package. >> Alas I don't see any 64bit package. > > The 32bit binaries will run

[sqlite] Version 3.12.0 coming soon

2016-03-22 Thread Richard Hipp
The status board for SQLite version 3.12.0 (https://www.sqlite.org/checklists/312/index) is now active. The release will occur when all items go green. The "Pre-Release Snapshot" over at https://www.sqlite.org/download.html contains the latest code. A preview of the change log can be seen

[sqlite] sqldiff nowadays

2016-03-22 Thread MM
Hello, I can see sqldiff appearing here: https://www.sqlite.org/sqldiff.html and in the downloads page as part of a linux 32bit binary package. Alas I don't see any 64bit package. Given a distro-installed 64bit sqlite binary and libs, which part of the sources would 1 need to download only

[sqlite] Article about pointer abuse in SQLite

2016-03-22 Thread Marc L. Allen
I don't think compilers "run" your code. When looking for uninitialized variables, it simply looks for a potential path through the code that uses a variable without it being initialized. The fact that the code never actually allows that path to occur is beyond the scope of most compilers,

[sqlite] Article about pointer abuse in SQLite

2016-03-22 Thread Adam Devita
It may be pedantic, but VS2016 will stop complaining if you edit your definition of s to large_struct s=new large_struct(); //set s to an actual instance of large_struct. c people can think of s as a pointer, and in c# the members are set to their default values. J Decker's point could also have

[sqlite] Article about pointer abuse in SQLite

2016-03-22 Thread Cezary H. Noweta
Hello, On 2016-03-22 00:35, James K. Lowden wrote: >[...] An example from Clang's discussion is > > int i = 10 << 31; Could you provide a link for that discussion? (Or google's phrase to retrieve such link?) -- best regards Cezary H. Noweta

[sqlite] Reserved column names

2016-03-22 Thread Dominique Devienne
On Tue, Mar 22, 2016 at 8:45 AM, Dominique Devienne wrote: > On Tue, Mar 22, 2016 at 12:36 AM, James K. Lowden < > jklowden at schemamania.org> wrote: > >> Roger's APSW is SQLIte specific. It's pretty easy to imagine, isn't >> it, that >> >> char sql[] = "select [col] from [foo]"; >> >>

[sqlite] Reserved column names

2016-03-22 Thread Dominique Devienne
On Tue, Mar 22, 2016 at 12:36 AM, James K. Lowden wrote: > Roger's APSW is SQLIte specific. It's pretty easy to imagine, isn't > it, that > > char sql[] = "select [col] from [foo]"; > > is easier for him to use than > > char sql[] = "select \"col\" from \"foo\""; > > even if

[sqlite] Article about pointer abuse in SQLite

2016-03-22 Thread J Decker
On Tue, Mar 22, 2016 at 6:58 AM, Adam Devita wrote: > It may be pedantic, but VS2016 will stop complaining if you edit your > definition of s to > large_struct s=new large_struct(); //set s to an actual instance of > large_struct. c people can think of s as a pointer, and in c# the > members are

[sqlite] Article about pointer abuse in SQLite

2016-03-22 Thread J Decker
On Tue, Mar 22, 2016 at 4:27 AM, Scott Doctor wrote: > > It is uninitialized. you are setting an initial value within an if > statement. For the compiler, the code has NOT actually executed. so it does > not use the value of the variable arbitrary_true_false. If it was a #define > then it would

[sqlite] sqldiff nowadays

2016-03-22 Thread Richard Hipp
On 3/22/16, MM wrote: > Hello, > I can see sqldiff appearing here: > > https://www.sqlite.org/sqldiff.html > > and in the downloads page as part of a linux 32bit binary package. > Alas I don't see any 64bit package. The 32bit binaries will run fine on 64bit machines. > > Given a

[sqlite] Article about pointer abuse in SQLite

2016-03-22 Thread Scott Doctor
It is uninitialized. you are setting an initial value within an if statement. For the compiler, the code has NOT actually executed. so it does not use the value of the variable arbitrary_true_false. If it was a #define then it would use the value but still give an error because it is not a

[sqlite] big table schema raise memory leak

2016-03-22 Thread matoung
hi , i m use sqlite 3.8.10.2 on suse 11 with jdk 1.8 jni, when i create much more tables,eg 200k, it can easily found the memory leak when close runed, but when i try linux native c code, it qppears correctly, it really confused me , could anybody tell the diffrence from jni runtime between