Re: [sqlite] Insert multiple values as an economy of coding time and quicker upload process ?

>I'm not an expert in SQLite extension. >Unless I missed something, Wholenumber seems apparently not embeded >into SQLite for python : >CREATE VIRTUAL TABLE nums USING wholenumber; >SELECT value FROM nums WHERE value<1; >SELECT value FROM nums WHERE value BETWEEN 100 AND 500 >gives : >

Re: [sqlite] Insert multiple values as an economy of coding time and quicker upload process ?

I'm not an expert in SQLite extension. Unless I missed something, Wholenumber seems apparently not embeded into SQLite for python : CREATE VIRTUAL TABLE nums USING wholenumber; SELECT value FROM nums WHERE value<1; SELECT value FROM nums WHERE value BETWEEN 100 AND 500 gives :

Re: [sqlite] Insert multiple values as an economy of coding time and quicker upload process ?

> >INSERT INTO t1 SELECT 1 UNION SELECT 2 UNION (...) SELECT ; > >It works out of the box on any DBMS you care to name, and of course in >SQLite, too. It is ever so slightly verbose, but better than the >alternative of executing INSERT INTO t1 VALUES(###); > Of course, if your

Re: [sqlite] Insert multiple values as an economy of coding time and quicker upload process ?

INSERT INTO t1 SELECT 1 UNION SELECT 2 UNION (...) SELECT ; It works out of the box on any DBMS you care to name, and of course in SQLite, too. It is ever so slightly verbose, but better than the alternative of executing INSERT INTO t1 VALUES(###); Cheers, -Tiago On Mon,

Re: [sqlite] Insert multiple values as an economy of coding time and quicker upload process ?

Yes, I was talking of the very test script that were written last friday : [a26f399ba4] like : do_execsql_test 4.1 { DROP TABLE IF EXISTS t1; CREATE TABLE t1(x); INSERT INTO t1 VALUES(1); INSERT INTO t1 VALUES(2); INSERT INTO t1 VALUES(3); INSERT

Re: [sqlite] Insert multiple values as an economy of coding time and quicker upload process ?

On Mon, Jan 13, 2014 at 12:21 PM, big stone wrote: > Hello, > > I read the source code of sqlite and I find a lot of : > > > CREATE TABLE t1(x INTEGER); > INSERT INTO t1 VALUES(1);INSERT INTO t1 VALUES(2); > > Are you talking about code in the test scripts? > >

Re: [sqlite] Insert multiple values as an economy of coding time and quicker upload process ?

On 13 Jan 2014, at 5:21pm, big stone wrote: > Wouldn't it be both an economy of coding time and a more quick upload > process to allow Multiple inserts SYNTAX ? > > like : > INSERT INTO t1 VALUES(1),(2), (); That does actually work. See the syntax diagram at

Re: [sqlite] Insert multiple values as an economy of coding time and quicker upload process ?

On 1/13/14 9:21 AM, "big stone" wrote: >Hello, > >I read the source code of sqlite and I find a lot of : > > >CREATE TABLE t1(x INTEGER); >INSERT INTO t1 VALUES(1);INSERT INTO t1 VALUES(2); > > >Wouldn't it be both an economy of coding time and a more quick upload

[sqlite] Insert multiple values as an economy of coding time and quicker upload process ?

Hello, I read the source code of sqlite and I find a lot of : CREATE TABLE t1(x INTEGER); INSERT INTO t1 VALUES(1);INSERT INTO t1 VALUES(2); Wouldn't it be both an economy of coding time and a more quick upload process to allow Multiple inserts SYNTAX ? like : INSERT INTO t1