lite.org] On Behalf Of petern
>>Sent: Sunday, 10 December, 2017 22:37
>>To: SQLite mailing list
>>Subject: Re: [sqlite] Retrieving constraint name
>>
>>Igor/Cezary,
>>
>>It is remarkable how 'struct Parse' already contains the constraint
>>name as
>
Hello,
On 2018-01-07 23:35, Igor Korot wrote:
Then maybe it could be considered to be included in the main tree by
simply applying the patch.
I'm afraid that if I change the order of fields in my patch, then it
will not help. Exchanging the fields in the pragma is trivial. The whole
patch
Hi, Cezary et al,
On Mon, Dec 11, 2017 at 5:48 PM, Cezary H. Noweta wrote:
> Hello,
>
> On 2017-12-11 04:29, Igor Korot wrote:
>>
>> Thank you, but I need to keep the official SQLite code.
>
> Anyway, for the people who are interested in foreign key names:
>
On Mon, Dec 11, 2017 at 4:48 PM, Cezary H. Noweta wrote:
> Hello,
>
> On 2017-12-11 04:29, Igor Korot wrote:
>>
>> Thank you, but I need to keep the official SQLite code.
>
> Anyway, for the people who are interested in foreign key names:
> http://sqlite.chncc.eu/fknames/.
Hello,
On 2017-12-11 04:29, Igor Korot wrote:
Thank you, but I need to keep the official SQLite code.
Anyway, for the people who are interested in foreign key names:
http://sqlite.chncc.eu/fknames/. Certainly, all tests expecting original
output of ``PRAGMA foreign_key_list'' will fail.
--
On Behalf Of petern
>Sent: Sunday, 10 December, 2017 22:37
>To: SQLite mailing list
>Subject: Re: [sqlite] Retrieving constraint name
>
>Igor/Cezary,
>
>It is remarkable how 'struct Parse' already contains the constraint
>name as
>Cezary pointed out.
>-> Token constrai
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
Hi,
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 above).
Does the info for the aforementioned
13 matches
Mail list logo