Re: [sqlite] FOREING KEY constraint

2017-07-03 Thread Paul Sanderson
-Original Message- > > From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > > On Behalf Of Clemens Ladisch > > Sent: Monday, 3 July, 2017 08:00 > > To: sqlite-users@mailinglists.sqlite.org > > Subject: Re: [sqlite] FOREING KEY constr

Re: [sqlite] FOREING KEY constraint

2017-07-03 Thread Keith Medcalf
ch > Sent: Monday, 3 July, 2017 08:00 > To: sqlite-users@mailinglists.sqlite.org > Subject: Re: [sqlite] FOREING KEY constraint > > J. King wrote: > > The sqlite_master table should have this information. > > > > SELECT count() FROM sqlite_master WHERE n

Re: [sqlite] FOREING KEY constraint

2017-07-03 Thread Keith Medcalf
-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > On Behalf Of J. King > Sent: Monday, 3 July, 2017 07:51 > To: SQLite mailing list > Subject: Re: [sqlite] FOREING KEY constraint > > The sqlite_master table should have this information. > > SELECT count()

Re: [sqlite] FOREING KEY constraint

2017-07-03 Thread Clemens Ladisch
J. King wrote: > The sqlite_master table should have this information. > > SELECT count() FROM sqlite_master WHERE name IS your_constraint_name AND > tbl_name IS your_table_name; Constraints do not have separate entries in the sqlite_master table. And there is no other mechanism to get this

Re: [sqlite] FOREING KEY constraint

2017-07-03 Thread J. King
; On Behalf Of Simon Slavin >>> Sent: Monday, 3 July, 2017 04:49 >>> To: SQLite mailing list >>> Subject: Re: [sqlite] FOREING KEY constraint >>> >>> >>> >>> On 3 Jul 2017, at 4:37am, Keith Medcalf <kmedc...@dessus.com> wrot

Re: [sqlite] FOREING KEY constraint

2017-07-03 Thread Igor Korot
on Slavin >> Sent: Monday, 3 July, 2017 04:49 >> To: SQLite mailing list >> Subject: Re: [sqlite] FOREING KEY constraint >> >> >> >> On 3 Jul 2017, at 4:37am, Keith Medcalf <kmedc...@dessus.com> wrote: >> >> > What do you mean "check for

Re: [sqlite] FOREING KEY constraint

2017-07-03 Thread Keith Medcalf
s-boun...@mailinglists.sqlite.org] > On Behalf Of Simon Slavin > Sent: Monday, 3 July, 2017 04:49 > To: SQLite mailing list > Subject: Re: [sqlite] FOREING KEY constraint > > > > On 3 Jul 2017, at 4:37am, Keith Medcalf <kmedc...@dessus.com> wrote: > > > What do you mea

Re: [sqlite] FOREING KEY constraint

2017-07-03 Thread Simon Slavin
On 3 Jul 2017, at 4:37am, Keith Medcalf wrote: > What do you mean "check for uniqueness? If you give two constraints the same name, does SQLite A) Ignore the problem B) Reject the second one complaining "duplicate name" C) Replace the first one with the second Simon.

Re: [sqlite] FOREING KEY constraint

2017-07-02 Thread Keith Medcalf
ssion of SQLite Database > Subject: [sqlite] FOREING KEY constraint > > Hi, ALL, > Is SQLite supports naming a foreign key constraint? > And if it does - is there a way to check for its uniqueness? > > Thank you. > ___ >

Re: [sqlite] FOREING KEY constraint

2017-07-02 Thread Keith Medcalf
.sqlite.org] > On Behalf Of Igor Korot > Sent: Sunday, 2 July, 2017 21:12 > To: Discussion of SQLite Database > Subject: [sqlite] FOREING KEY constraint > > Hi, ALL, > Is SQLite supports naming a foreign key constraint? > And if it does - is there a way to check

[sqlite] FOREING KEY constraint

2017-07-02 Thread Igor Korot
Hi, ALL, Is SQLite supports naming a foreign key constraint? And if it does - is there a way to check for its uniqueness? Thank you. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org