Re: database constraints - Mailing list pgsql-general

From Joshua D. Drake
Subject Re: database constraints
Date
Msg-id 41641E02.8060301@commandprompt.com
Whole thread Raw
In response to Re: database constraints  (David Fetter <david@fetter.org>)
Responses Re: database constraints  (David Fetter <david@fetter.org>)
List pgsql-general
>
>
> What's "reasonable?" ;)
>
> BTW, "id" is a terrible name for a column.  Better call it foo_id.

Hello,

I disagree with the idea that "id" is a terrible name for a column. The
only negative to it, is that you will have to be explicit in your
declarations when doing joins and such... ex:

SELECT * FROM foo
    JOIN bar on (foo.id = bar.id)

Personally I would rather see, and write that then:

SELECT * FROM foo
    JOIN bar on (foo_id = bar_id)


Sincerely,

Joshua D. Drake



>
> Cheers,
> D


--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL

Attachment

pgsql-general by date:

Previous
From: Mark Gibson
Date:
Subject: Re: Cache lookup failed for relation, when trying to DROP
Next
From: David Fetter
Date:
Subject: Re: database constraints