On 17 Sep 2011, at 7:28pm, Petite Abeille wrote:
> (5) contextually typed row value expression list
>
> http://savage.net.au/SQL/sql-99.bnf.html#contextually%20typed%20row%20value%20expression%20list
>
> ::=
>
> [ { }... ]
>
> (6) contextually typed row value
On Sep 17, 2011, at 8:43 PM, Mr. Puneet Kishor wrote:
> All this chattering among us doesn't really matter (other than for academic
> purposes).
For the, hmmm, more scholarly inclined on the list, a marginally more readable
ISO spec, ISO/IEC 9075-2:2003:
On Sep 17, 2011, at 1:06 PM, Simon Slavin wrote:
>
> On 17 Sep 2011, at 6:42pm, Petite Abeille wrote:
>
>> On Sep 17, 2011, at 7:33 PM, Simon Slavin wrote:
>>
>>> As was clear from my post, I was referring to SQL standards. What various
>>> implementation vendors choose to do is up to them.
On Sep 17, 2011, at 8:06 PM, Simon Slavin wrote:
> ::=| |
>
>
> ? Which one, and where is the expansion that allows for multiple sets of
> brackets after "VALUES" ?
If I'm reading this correctly, the constructor one.
Step by step:
(1) insert statement
On 17 Sep 2011, at 6:42pm, Petite Abeille wrote:
> On Sep 17, 2011, at 7:33 PM, Simon Slavin wrote:
>
>> As was clear from my post, I was referring to SQL standards. What various
>> implementation vendors choose to do is up to them. But the multi-spec
>> syntax referred to in the OP is not
On Sep 17, 2011, at 7:33 PM, Simon Slavin wrote:
> As was clear from my post, I was referring to SQL standards. What various
> implementation vendors choose to do is up to them. But the multi-spec syntax
> referred to in the OP is not in any SQL standard I've seen.
In BNF Grammar for
On 17 Sep 2011, at 6:08pm, Petite Abeille wrote:
> On Sep 17, 2011, at 6:04 PM, Simon Slavin wrote:
>
>> Can you find the syntax that allows
>
> These ANSI specifications are notoriously difficult to pinpoint :)
Not really, they just cost money. For instance:
On Sep 17, 2011, at 6:04 PM, Simon Slavin wrote:
> Can you find the syntax that allows
These ANSI specifications are notoriously difficult to pinpoint :)
DB2:
http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/r970.htm
INSERT
INTO
On Sat, 17 Sep 2011 16:23:23 +0100, Simon Slavin
wrote:
>
>On 16 Sep 2011, at 8:27pm, Jim Michaels wrote:
>
>> INSERT is supposed to handle multiple rows for VALUES.
>> for example,
>> INSERT INTO table(digit,dialpadstr) VALUES
>> (2,'abc'),
>> (3,'def'),
>> (4,'ghi'),
>>
On 17 Sep 2011, at 4:52pm, Petite Abeille wrote:
> On Sep 17, 2011, at 5:11 PM, Igor Tandetnik wrote:
>
>> Supposed by whom? What is the basis for this claim?
>
> SQL-92:
>
> http://en.wikipedia.org/wiki/Insert_(SQL)#Multirow_inserts
Here's a draft of SQL-92. You can find the INSERT
On Sep 17, 2011, at 5:55 PM, Mr. Puneet Kishor wrote:
> Essentially, if I had my druthers, I would support whatever Pg supports and
> be done with it. For most part SQLite seems to follow "good for Pg good for
> the gander" philosophy.
I would much rather have a MERGE statement:
On Sep 17, 2011, at 10:33 AM, Simon Slavin wrote:
>
> On 17 Sep 2011, at 4:29pm, Mr. Puneet Kishor wrote:
>
>> The multiline INSERT capability may not be a SQL standard, but it is not
>> only highly convenient, it is also supported by Pg, the ostensible role
>> model and inspiration for
On Sep 17, 2011, at 5:11 PM, Igor Tandetnik wrote:
> Supposed by whom? What is the basis for this claim?
SQL-92:
http://en.wikipedia.org/wiki/Insert_(SQL)#Multirow_inserts
This feature is supported by DB2, SQL Server (since version 10.0 - i.e. 2008),
PostgreSQL (since version 8.2), MySQL,
On 17 Sep 2011, at 4:29pm, Mr. Puneet Kishor wrote:
> The multiline INSERT capability may not be a SQL standard, but it is not only
> highly convenient, it is also supported by Pg, the ostensible role model and
> inspiration for SQLite. Not that I particularly care either way because I
>
On Sep 17, 2011, at 10:11 AM, Igor Tandetnik wrote:
> Jim Michaels
>
> wrote:
>> INSERT is supposed to handle multiple rows for VALUES.
>
> Supposed by whom? What is the basis for this claim?
The multiline INSERT
On 16 Sep 2011, at 8:27pm, Jim Michaels wrote:
> INSERT is supposed to handle multiple rows for VALUES.
> for example,
> INSERT INTO table(digit,dialpadstr) VALUES
> (2,'abc'),
> (3,'def'),
> (4,'ghi'),
> (5,'jkl'),
> (6,'mno'),
> (7,'pqrs'),
> (8,'tuv'),
> (9,'wxyz');
Can you find support for
Jim Michaels
wrote:
> INSERT is supposed to handle multiple rows for VALUES.
Supposed by whom? What is the basis for this claim?
--
Igor Tandetnik
___
sqlite-users
On Fri, 16 Sep 2011 12:27:35 -0700, Jim Michaels
wrote:
>INSERT is supposed to handle multiple rows for VALUES.
>for example,
>INSERT INTO table(digit,dialpadstr) VALUES
>(2,'abc'),
>(3,'def'),
>(4,'ghi'),
>(5,'jkl'),
>(6,'mno'),
>(7,'pqrs'),
>(8,'tuv'),
On Sep 16, 2011, at 9:27 PM, Jim Michaels wrote:
> currently, sqlite only handles 1 row.
> INSERT INTO table(digit,dialpadstr) VALUES
> (2,'abc');
try:
insert into foo ( bar )
select 1 as bar union all
select 2 as bar
etc...
Please refer back to the fine manual:
INSERT is supposed to handle multiple rows for VALUES.
for example,
INSERT INTO table(digit,dialpadstr) VALUES
(2,'abc'),
(3,'def'),
(4,'ghi'),
(5,'jkl'),
(6,'mno'),
(7,'pqrs'),
(8,'tuv'),
(9,'wxyz');
currently, sqlite only handles 1 row.
INSERT INTO table(digit,dialpadstr) VALUES
(2,'abc');
20 matches
Mail list logo