On Jan 4, 2014, at 11:34 PM, RSmith wrote:
> . I think in America the term "Captain Obvious" is used for the author of
> such a statement.
This sounds like a job for ObviousMan!
http://treesflowersbirds.files.wordpress.com/2010/01/obviousman.jpg
> things _are_ moving
On 2014/01/05 00:03, Petite Abeille wrote:
Things change. Syntax evolves. Languages matures, even SQL. The ‘with’ clause is a change for the better. As is merge. As are
windowing functions. SQLite cannot pretend it’s 1986 forever. It has to move with the times or it will become ossified,
On Jan 4, 2014, at 8:05 PM, James K. Lowden wrote:
> That's an aesthetic judgement. Even if I agreed, it doesn't change the
> fact that every language feature is an element of complexity,
> and redundant language features are needless complexity.
Things change.
At 24f84b38131866f7b435ffe641bb2f6991a70db2 the function setEstimatedRows was
added to fts3.c. This function is already defined so the amalgamation build
fails with a duplicate function definition.
At 4e725f53131d3584319c710c8710a068989543c6 expr.c 3391 sqlite3ExplainPop was
set to have two
On Wed, 1 Jan 2014 23:23:04 +0100
Petite Abeille wrote:
> Yes, a ?with? clause is just syntax sugar providing named subqueries.
> But this sugar open the door to drastically different ways to write
> queries, bringing structure, clarity of thoughts and purpose to
>
On Thu, 2 Jan 2014 01:29:52 +
Simon Slavin wrote:
> Hmm. Even
>
> update t set i = i + 1 - 1
>
> with i being UNIQUE might be a good test case.
Well, that actually works:
sqlite> create table t (t int primary key);
sqlite> insert into t values (1);
sqlite> insert
On 01/04/2014 03:23 PM, E. Timothy Uy wrote:
This is a class of problems I started seeing around 3.8.x. Any insights
would be much appreciated. Sometimes it happens when there are more than a
few INNER JOINS, others, in the case, happen when I ORDER BY the virtual
table's docid. I feel like this
Hello.
During compilation, the warning occurs
sqlite3.c: In function 'deserializeGeometry':
sqlite3.c:142353: warning: assignment from incompatible pointer type
for the sources of http://www.sqlite.org/2013/sqlite-autoconf-3080200.tar.gz
with -DSQLITE_RTREE_INT_ONLY=1
and really
142314 /*
This is a class of problems I started seeing around 3.8.x. Any insights
would be much appreciated. Sometimes it happens when there are more than a
few INNER JOINS, others, in the case, happen when I ORDER BY the virtual
table's docid. I feel like this used to work.
SQLite version 3.8.2 2013-12-06
9 matches
Mail list logo