Re: [sqlite] Details on New Features

2012-05-06 Thread Gabor Grothendieck
On Sun, May 6, 2012 at 8:00 PM, Donald Griggs wrote: > Regarding:   What precisely are the > "improvements" in handling of CSV inputs? > > > Gabor, I don't know about "precisely" -- I'll let others on the list tell > me where I'm off, but here's my take: > > > A lot of strange

Re: [sqlite] Details on New Features

2012-05-06 Thread Donald Griggs
Regarding: What precisely are the "improvements" in handling of CSV inputs? Gabor, I don't know about "precisely" -- I'll let others on the list tell me where I'm off, but here's my take: A lot of strange things call themselves csv, but the change attempts to make the sqlite3 utility's CSV

Re: [sqlite] Details on New Features

2012-05-04 Thread Nico Williams
On Fri, May 4, 2012 at 4:04 PM, Richard Hipp wrote: > Correction:  The one that it encounters first, since subsequent rows of the > same value will not trigger a new copy of values into the output registers, > since only a new min/max does that. But surely that's

Re: [sqlite] Details on New Features

2012-05-04 Thread Richard Hipp
On Fri, May 4, 2012 at 5:02 PM, Richard Hipp wrote: > > > On Fri, May 4, 2012 at 5:01 PM, Ralf Junker wrote: > >> On 04.05.2012 16:39, Richard Hipp wrote: >> >> > If a single min() or max() aggregate function appears in a query, then >> any >> > other columns

Re: [sqlite] Details on New Features

2012-05-04 Thread Igor Tandetnik
On 5/4/2012 5:01 PM, Ralf Junker wrote: On 04.05.2012 16:39, Richard Hipp wrote: If a single min() or max() aggregate function appears in a query, then any other columns that are not contained within aggregate functions and that are not elements of the GROUP BY will take values from one of the

Re: [sqlite] Details on New Features

2012-05-04 Thread Richard Hipp
On Fri, May 4, 2012 at 5:01 PM, Ralf Junker wrote: > On 04.05.2012 16:39, Richard Hipp wrote: > > > If a single min() or max() aggregate function appears in a query, then > any > > other columns that are not contained within aggregate functions and that > > are not elements of

Re: [sqlite] Details on New Features

2012-05-04 Thread Marc L. Allen
The last one it saw. It's not deterministic. > -Original Message- > From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users- > boun...@sqlite.org] On Behalf Of Ralf Junker > Sent: Friday, May 04, 2012 5:01 PM > To: General Discussion of SQLite Database > Subject: Re

Re: [sqlite] Details on New Features

2012-05-04 Thread Ralf Junker
On 04.05.2012 16:39, Richard Hipp wrote: > If a single min() or max() aggregate function appears in a query, then any > other columns that are not contained within aggregate functions and that > are not elements of the GROUP BY will take values from one of the same rows > that satisfied the one

Re: [sqlite] Details on New Features

2012-05-04 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/05/12 09:42, Nico Williams wrote: > A pragma by which to cause SQLite3 to return an error instead might be > useful, but then, it's SQL_Lite_. What I have always wanted for SQLite is some sort of "lint" mode. It would tell you when your

Re: [sqlite] Details on New Features

2012-05-04 Thread Richard Hipp
On Fri, May 4, 2012 at 12:44 PM, Eric Sink wrote: > > Is this new syntax likely to perform any better than the traditional way > of writing the query? > Dunno. Depends on which "traditional way" you are talking about, I suppose. Here's how it works: SQLite internally

Re: [sqlite] Details on New Features

2012-05-04 Thread Eric Sink
Is this new syntax likely to perform any better than the traditional way of writing the query? -- E On May 4, 2012, at 11:42 AM, Nico Williams wrote: > On Fri, May 4, 2012 at 9:20 AM, Richard Hipp wrote: >>> Queries of the form: "SELECT

Re: [sqlite] Details on New Features

2012-05-04 Thread Nico Williams
On Fri, May 4, 2012 at 9:20 AM, Richard Hipp wrote: >>         Queries of the form: "SELECT max(x), y FROM table" returns the >> value of y on the same row that contains the maximum x value. >> >> Is that standard SQL behavior?  I'd have expected that to return one row >> for

Re: [sqlite] Details on New Features

2012-05-04 Thread Gabor Grothendieck
On Fri, May 4, 2012 at 10:46 AM, Gabor Grothendieck wrote: > On Fri, May 4, 2012 at 10:39 AM, Richard Hipp wrote: >> On Fri, May 4, 2012 at 10:33 AM, Gabor Grothendieck >> wrote: >> >>> On Fri, May 4, 2012 at 10:20 AM, Richard

Re: [sqlite] Details on New Features

2012-05-04 Thread Richard Hipp
On Fri, May 4, 2012 at 10:33 AM, Gabor Grothendieck wrote: > On Fri, May 4, 2012 at 10:20 AM, Richard Hipp wrote: > > On Fri, May 4, 2012 at 10:06 AM, Rob Richardson < > rdrichard...@rad-con.com>wrote: > > > >> Gabor Grothendieck mentioned a new

Re: [sqlite] Details on New Features

2012-05-04 Thread Gabor Grothendieck
On Fri, May 4, 2012 at 10:20 AM, Richard Hipp wrote: > On Fri, May 4, 2012 at 10:06 AM, Rob Richardson > wrote: > >> Gabor Grothendieck mentioned a new feature of SQLite in 3.7.11: >>         Queries of the form: "SELECT max(x), y FROM table" returns

Re: [sqlite] Details on New Features

2012-05-04 Thread Richard Hipp
On Fri, May 4, 2012 at 10:06 AM, Rob Richardson wrote: > Gabor Grothendieck mentioned a new feature of SQLite in 3.7.11: > Queries of the form: "SELECT max(x), y FROM table" returns the > value of y on the same row that contains the maximum x value. > > Is that

Re: [sqlite] Details on New Features

2012-05-04 Thread Rob Richardson
Gabor Grothendieck mentioned a new feature of SQLite in 3.7.11: Queries of the form: "SELECT max(x), y FROM table" returns the value of y on the same row that contains the maximum x value. Is that standard SQL behavior? I'd have expected that to return one row for every row in the

[sqlite] Details on New Features

2012-05-04 Thread Gabor Grothendieck
In this link: http://sqlite.org/releaselog/3_7_11.html it refers to these new features: Queries of the form: "SELECT max(x), y FROM table" returns the value of y on the same row that contains the maximum x value. Improvements to the handling of CSV inputs in the command-line shell Is there