Re: [sqlite] select 1 where 1 - 1;

On 2014/05/06 06:47, Scott Robison wrote: Except it doesn't, because C compilers can warn when you type "if (var = constant) ...;" when you probably meant "if (var == constant) ...;". If at least some C compiler implementations can do that within the confines of the ANSI C 89 standard, SQLite

Re: [sqlite] select 1 where 1 - 1;

On Mon, May 5, 2014 at 9:07 PM, Jay Kreibich wrote: > > On May 5, 2014, at 6:16 PM, Scott Robison wrote: > > > On Mon, May 5, 2014 at 4:15 PM, Jay Kreibich wrote: > > > >> So far this whole discussion seems to boiled down to the fact

Re: [sqlite] select 1 where 1 - 1;

On May 5, 2014, at 6:16 PM, Scott Robison wrote: > On Mon, May 5, 2014 at 4:15 PM, Jay Kreibich wrote: > >> So far this whole discussion seems to boiled down to the fact that SQLite >> doesn’t have a native Boolean type. That’s it. No, it doesn’t.

Re: [sqlite] Windows Phone 8.1

Thank you Joe -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Joe Mistachkin Sent: Monday, May 5, 2014 8:23 PM To: 'General Discussion of SQLite Database' Subject: Re: [sqlite] Windows Phone 8.1 Ryan Finnesey wrote: > >

Re: [sqlite] Windows Phone 8.1

Ryan Finnesey wrote: > > Has anyone confirmed this is something in the works? > It's actively being worked on. -- Joe Mistachkin ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] select 1 where 1 - 1;

On Mon, May 5, 2014 at 4:15 PM, Jay Kreibich wrote: > So far this whole discussion seems to boiled down to the fact that SQLite > doesn’t have a native Boolean type. That’s it. No, it doesn’t. Once we > accept that, everything else makes perfect sense based off existing >

Re: [sqlite] select 1 where 1 - 1;

Hihihi, some folks do not share the same references, anyway yes 3 passes that's named super bowle, LOL (warning many bad jokes inside) On Mon, May 5, 2014 at 3:31 PM, Petite Abeille wrote: > > On May 6, 2014, at 12:15 AM, Jay Kreibich wrote: > > >

Re: [sqlite] select 1 where 1 - 1;

On May 6, 2014, at 12:15 AM, Jay Kreibich wrote: > Cross what bridge? http://www.youtube.com/watch?v=zKhEw7nD9C4 > You seem to be trying to use common sense and semantic meaning to make an > argument. To quote an old CS prof, “If you argue in English**, you’re > wrong.”

Re: [sqlite] select 1 where 1 - 1;

On May 5, 2014, at 3:03 PM, Petite Abeille wrote: > > On May 5, 2014, at 9:15 PM, RSmith wrote: > >> Je suis desole mon ami… > > Moi aussi :P > > I have no quarrel with you, good Sir Knight, but I must cross this bridge: > > select 1 where 1

Re: [sqlite] Windows Phone 8.1

Has anyone confirmed this is something in the works? -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Andrew Arnott Sent: Sunday, May 4, 2014 6:22 PM To: General Discussion of SQLite Database Cc: Lane Williams Subject: Re:

Re: [sqlite] NOP INSERT still writes to the DB/journal

On Mon, May 5, 2014 at 4:53 PM, Patrick Donnelly wrote: > Hi, > > I have an INSERT that looks like > > INSERT INTO T > SELECT ... > > which I'm running numerous times a second that generally does nothing > because the SELECT returns no rows. Unfortunately, I've found

Re: [sqlite] select 1 where 1 - 1;

LOL be careful not to break the stinger and leave it buried in the skin. Hello Petite Abeille, when you "eval" an expression, are you doing from the right or on the lvalue. Best. On Mon, May 5, 2014 at 1:03 PM, Petite Abeille wrote: > > On May 5, 2014, at 9:15

[sqlite] NOP INSERT still writes to the DB/journal

Hi, I have an INSERT that looks like INSERT INTO T SELECT ... which I'm running numerous times a second that generally does nothing because the SELECT returns no rows. Unfortunately, I've found that SQLite still does numerous disk writes anyway in this situation. Is my only option to

Re: [sqlite] select 1 where 1 - 1;

On May 5, 2014, at 9:15 PM, RSmith wrote: > Je suis desole mon ami… Moi aussi :P I have no quarrel with you, good Sir Knight, but I must cross this bridge: select 1 where 1 is 1; select 1 where 1 is not 1; select 1 where 1 is ( 1 = 1 ); select 1 in ( null ); — oh…

Re: [sqlite] select 1 where 1 - 1;

On 2014/05/05 20:46, Petite Abeille wrote: On May 5, 2014, at 8:21 PM, RSmith wrote: the idea that introducing more complication will make erros/bugs less is just false. Straw man argument, unrelated to the topic at hand. Je suis desole mon ami... That comment was not

Re: [sqlite] select 1 where 1 - 1;

I think everyone agrees that SQLite does not strictly follow the SQL standards for WHERE clause expressions. The question is... should it? One must ask, "what makes SQLite lite?" I think this kind of simplification is of them. However, I can understand that it might rankle some people.

Re: [sqlite] select 1 where 1 - 1;

On May 5, 2014, at 8:21 PM, RSmith wrote: > the idea that introducing more complication will make erros/bugs less is just > false. Straw man argument, unrelated to the topic at hand. This is solely about the SQL parser failing short of reporting syntax errors for

Re: [sqlite] select 1 where 1 - 1;

On 2014/05/05 20:00, Richard Hipp wrote: I am deeply committed to the concept that simpler is better. And I am deeply skeptical of arguments that making a language more complex by adding new type rules does anything to reduce bugs. To add to this, I have heard a lot of proponents on both

Re: [sqlite] select 1 where 1 - 1;

On May 5, 2014, at 8:00 PM, Richard Hipp wrote: > Petite's complaint is that in most other SQL database engines, 0 is not > false. If you try to use 0 where a boolean is needed, you get a syntax > error. In strict SQL, boolean and integer are incompatible types that > cannot

Re: [sqlite] select 1 where 1 - 1;

On May 5, 2014 11:36 AM, "Stephan Beal" wrote: > > I mean ‘where 1’, or ‘where ‘1 - 1’, or ‘where null’, or ‘where 0 / 0’, or > > any of this nonsense. There is nothing to compare. It’s nonsensical. > > Oh, but there is: 1-1 is an expression, the result of which is integer

Re: [sqlite] select 1 where 1 - 1;

On Mon, May 5, 2014 at 1:36 PM, Stephan Beal wrote: > On Mon, May 5, 2014 at 7:31 PM, Petite Abeille >wrote: > > > On May 5, 2014, at 7:15 PM, Stephan Beal wrote: > > > Why expect an error? It's abstractly the same as

Re: [sqlite] select 1 where 1 - 1;

The WHERE clause takes only one parameter. WHERE expects an expression, which evaluates down to one value. That expression does not need to be a comparison. It commonly is, but it can be anything, such as a CASE expression, an EXISTS subselect, or a function. As far as SQLite cares, all

Re: [sqlite] select 1 where 1 - 1;

On May 5, 2014, at 7:36 PM, Stephan Beal wrote: > Oh, but there is: 1-1 is an expression, the result of which is integer 0 It’s nonsensical as a where clause expression. > (as opposed to string '0'), which, in all programming environments except, > IIRC, Xenix, is

Re: [sqlite] select 1 where 1 - 1;

On Mon, May 5, 2014 at 7:31 PM, Petite Abeille wrote: > On May 5, 2014, at 7:15 PM, Stephan Beal wrote: > > Why expect an error? It's abstractly the same as saying WHERE 'a' = 'b’, > > I mean ‘where 1’, or ‘where ‘1 - 1’, or ‘where null’, or

Re: [sqlite] select 1 where 1 - 1;

On May 5, 2014, at 7:15 PM, Stephan Beal wrote: > Why expect an error? It's abstractly the same as saying WHERE 'a' = 'b’, I mean ‘where 1’, or ‘where ‘1 - 1’, or ‘where null’, or ‘where 0 / 0’, or any of this nonsense. There is nothing to compare. It’s nonsensical.

Re: [sqlite] select 1 where 1 - 1;

On Mon, May 5, 2014 at 6:56 PM, Petite Abeille wrote: > > select 1 where 1 = 1; > > Indeed. I would have expected a syntax error along the lines of 'invalid > relational operator’ or such. And that’s that. > Why expect an error? It's abstractly the same as saying

Re: [sqlite] select 1 where 1 - 1;

On May 5, 2014, at 1:14 AM, James K. Lowden wrote: > To amplify the point, the issue isn't pure fussiness or obligation to > adhere to standards. A permissive parser invites error. Exactly. > It's not hard to imagine > > select 1 where 1 - 1; > > was

Re: [sqlite] select 1 where 1 - 1;

On Mon, May 5, 2014 at 11:35 AM, Marc L. Allen wrote: > Really? Interesting. > > So... > > Select 1 Where 1 < inf; ? > > Or is it just when taking inf by itself? > Maybe I'm wrong. It's division by 0.0 that gives NULL as an answer. Perhaps if you insert an inf

Re: [sqlite] select 1 where 1 - 1;

Really? Interesting. So... Select 1 Where 1 < inf; ? Or is it just when taking inf by itself? -Original Message- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Richard Hipp Sent: Monday, May 05, 2014 11:32 AM To: General Discussion of

Re: [sqlite] select 1 where 1 - 1;

On Mon, May 5, 2014 at 11:28 AM, mm.w <0xcafef...@gmail.com> wrote: > select inf; should be true or false? :) > Neither true nor false. SQLite considers infinity to be the same as NULL. -- D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing

Re: [sqlite] select 1 where 1 - 1;

I know Simon, just asking, nope an empty string is a valid string, else you say no NULL allowed for strings, might be a backend option 8) On Mon, May 5, 2014 at 8:27 AM, Simon Slavin wrote: > > On 5 May 2014, at 4:18pm, mm.w <0xcafef...@gmail.com> wrote: > > > "an empty

Re: [sqlite] select 1 where 1 - 1;

select inf; should be true or false? :) On Mon, May 5, 2014 at 8:18 AM, mm.w <0xcafef...@gmail.com> wrote: > Hello, > > "an empty string should be false" strongly disagree, a NULL string should > be solely false, now in this case, the question is: comparisons should be > handled as bin or by;

Re: [sqlite] select 1 where 1 - 1;

On 5 May 2014, at 4:18pm, mm.w <0xcafef...@gmail.com> wrote: > "an empty string should be false" strongly disagree, a NULL string should > be solely false, now in this case, the question is: comparisons should be > handled as bin or by; 'literal' values? or equality/comparison must not be >

Re: [sqlite] select 1 where 1 - 1;

Hello, "an empty string should be false" strongly disagree, a NULL string should be solely false, now in this case, the question is: comparisons should be handled as bin or by; 'literal' values? or equality/comparison must not be eval'ed and strictly made on type? one other of the quirk would

Re: [sqlite] sqlite3_bind_text issue

>-Ursprüngliche Nachricht- >Von: lyx [mailto:sdu...@163.com] >Gesendet: Montag, 05. Mai 2014 05:00 >An: sqlite-users@sqlite.org >Betreff: Re: [sqlite] sqlite3_bind_text issue > >I have tried to use SQL_TRANSIENT instead of SQLITE_STATIC in >sqlite3_bind_text. But the result is still not

Re: [sqlite] sqlite3_bind_text issue

A Dilluns, 5 de maig de 2014 02:59:59, lyx va escriure: > I have tried to use SQL_TRANSIENT instead of SQLITE_STATIC in > sqlite3_bind_text. But the result is still not correct. The column num is > correct now but the row number embedded in column data in every row is all > assigned to zero now.

Re: [sqlite] Sqlite Crash In Windows Kernel

On 5 May 2014, at 6:42am, NULL wrote: > the attached files is the code i used,and the code would be cause system > crash when call like this, > sqlite3_exec(db, "create table hello(one varchar(10), two smallint)", > callback, 0, ) You cannot attach files to posts to

[sqlite] Sqlite Crash In Windows Kernel

Hi, the attached files is the code i used,and the code would be cause system crash when call like this, sqlite3_exec(db, "create table hello(one varchar(10), two smallint)", callback, 0, ) A snapshot of call stack on crash is attached. Zhouran

Re: [sqlite] Is it better that sqlite support share One Database Connection In Multithreads?

Imagine the following sequence on a "multi thread shared" connection. Thread A prepares a SELECT statement Thread A steps the statement a couple of times to retrieve some data Thread B comes along an finalizes the statement What do you propose should happen when thread A tries to step the

Re: [sqlite] FTS3/4 merge function behaviour when deleting rows

On 2 May 2014 10:22, Dan Kennedy wrote: > > > A query like: > > SELECT level, count(*) AS ntree FROM yourftstablename_segdir; > > will tell you how many b-trees there currently are at each level. Which > might help you figure out what is going on and when you might expect