You are still missing the point - "functional dependencies" is not a
separate module that can be turned on or off with code, they are inherent in
the database design. According to relational theory any non-key field on a
table is functionally dependent of the key of that table, so if you support
both key and non-key fields on a table then you automatically support
functional dependencies. How can you possibly say otherwise?
Where does it describe in the SQL standards EXACTLY what the term
"functional dependencies" means? Is it the same as in relational theory, or
is it something different?
Tony Marston
http://www.tonymarston.net=20
http://www.radicore.org
> -----Original Message-----
> From: Greg Stark [mailto:greg.stark@enterprisedb.com] On=20
> Behalf Of Gregory Stark
> Sent: 15 October 2008 02:57
> To: Tony Marston
> Cc: 'Peter Eisentraut'; pgsql-bugs@postgresql.org
> Subject: Re: BUG #4465: GROUP BY is not to SQL standard
>=20
>=20
> "Tony Marston" <tony@marston-home.demon.co.uk> writes:
>=20
> > I think your definition of "Feature T301 Functional=20
> Dependencies" is=20
> > extremely questionable. ... If you support both key and non-key=20
> > columns on a table then you support functional dependencies whether=20
> > you like it or not.
>=20
> An ISO/IEC 9075 conformant implementation must list in its=20
> documentation which optional features it claims to support.=20
> Postgres does so at:
>=20
> http://www.postgresql.org/docs/8.3/static/features.html
>=20
> In particular note that T301 is listed partway down this list:
>=20
> http://www.postgresql.org/docs/8.3/static/unsupported-features
-sql-standard.html
> As soon as I point out an SQL standard that you DON'T follow I get a=20
> barrage of weasel words and pathetic excuses.
Well then.
--=20
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
