After stripping out comments and so forth of course ...
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of
Hi,
On Sun, Dec 10, 2017 at 11:36 PM, petern wrote:
> Igor/Cezary,
>
> It is remarkable how 'struct Parse' already contains the constraint name as
> Cezary pointed out.
> -> Token constraintName;/* Name of the constraint currently being parsed */
> But is not
Igor/Cezary,
It is remarkable how 'struct Parse' already contains the constraint name as
Cezary pointed out.
-> Token constraintName;/* Name of the constraint currently being parsed */
But is not included in the 'struct FKey' linked list node that is reeled in
to produce columns in the PRAGMA
Hi,
On Sun, Dec 10, 2017 at 8:30 PM, Cezary H. Noweta wrote:
> Hello,
>
> On 2017-12-11 01:04, Igor Korot wrote:
>
>> On Sun, Dec 10, 2017 at 5:01 PM, Cezary H. Noweta
>> wrote:
>
>
>>> On 2017-12-10 07:21, Igor Korot wrote:
>
>
The CREATE TABLE
Hello,
On 2017-12-11 01:04, Igor Korot wrote:
On Sun, Dec 10, 2017 at 5:01 PM, Cezary H. Noweta wrote:
On 2017-12-10 07:21, Igor Korot wrote:
The CREATE TABLE statement supports the following syntax:
CREATE TABLE( , CONSTRAINT FOREIGN
KEY() REFERENCES
Hi,
On Sun, Dec 10, 2017 at 5:01 PM, Cezary H. Noweta wrote:
> Hello,
>
> On 2017-12-10 07:21, Igor Korot wrote:
>>
>> The CREATE TABLE statement supports the following syntax:
>>
>> CREATE TABLE( , CONSTRAINT FOREIGN
>> KEY() REFERENCES (ref_column_list>);
>>
>> However,
Hello,
On 2017-12-10 07:21, Igor Korot wrote:
The CREATE TABLE statement supports the following syntax:
CREATE TABLE( , CONSTRAINT FOREIGN
KEY() REFERENCES (ref_column_list>);
However, the statement "PRAGME foreign_key_list;" does not list the
foreign key name ("fk_name" in the statement
Richard Hipp wrote:
On 12/10/17, javaj1...@elxala.com wrote:
According to the documentation UPDATE SET admits column-name-list as
argument
but I cannot get it working. Here some tries
DROP TABLE IF EXISTS test; CREATE TABLE test(a,b,c);
-- ok
UPDATE test SET a = "vala",
On 08-12-17 23:34, Scott Doctor wrote:
>
> Is it possible that the first call to random is cached and the cached
> value is being returned in subsequent calls?
>
> -
> Scott Doctor
> sc...@scottdoctor.com
> -
>
The easiest way to get this behaviour
>UPDATE test SET (a, b) = "vala", "valb" ;
Should that not be (a, b) = (‘vala’, ‘valb’);
>UPDATE test SET (a, b) = (SELECT "vala", "valb") ;
Should that not be (a, b) = ((SELECT ‘vala’), ‘valb’);
___
sqlite-users mailing list
On 12/10/17, javaj1...@elxala.com wrote:
>
> According to the documentation UPDATE SET admits column-name-list as
> argument
> but I cannot get it working. Here some tries
>
> DROP TABLE IF EXISTS test; CREATE TABLE test(a,b,c);
>
> -- ok
> UPDATE test SET a = "vala", b =
Hi,
According to the documentation UPDATE SET admits column-name-list as
argument
but I cannot get it working. Here some tries
DROP TABLE IF EXISTS test; CREATE TABLE test(a,b,c);
-- ok
UPDATE test SET a = "vala", b = "valb" ;
UPDATE test SET a = (SELECT "vala"), b = (SELECT "valb") ;
--
12 matches
Mail list logo