i, 14 Aug 2015 03:52:28 +0100, David G. Johnston
wrote:
On Thu, Aug 13, 2015 at 7:26 PM, Stephen Feyrer
wrote:
When we design databases, invariably, normally we design the queries at
the same time.
​Well this may be true to an extent well implemented models have the
ability to answe
On Fri, 14 Aug 2015 01:58:29 +0100, Adrian Klaver
wrote:
On 08/13/2015 05:40 PM, Stephen Feyrer wrote:
On Fri, 14 Aug 2015 01:14:12 +0100, Adrian Klaver
wrote:
On 08/13/2015 05:03 PM, Stephen Feyrer wrote:
Hi,
This is probably not an original question merely one which I haven't
On Fri, 14 Aug 2015 01:14:12 +0100, Adrian Klaver
wrote:
On 08/13/2015 05:03 PM, Stephen Feyrer wrote:
Hi,
This is probably not an original question merely one which I haven't
been able to find an answer for.
Basically, the question is why is there not an equivalent foreign key
conce
ould look something like:
SELECT user-name, email FROM profiles WITH-IMPLICIT-JOIN
When building our databases we already put a lot of work in normalising as
much as we can. Then after all that work we have to virtually start again
building up select, insert and update statements etc. all with all that
referential integrity in mind.
The advantages of a first class foreign key field as I see it are at least
two fold. One it make building and maintaining your database easier. Two
it is a means to provide some iterative structures easily coded.
To me this looks like a good idea.
--
Kind regards
Stephen Feyrer
