From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Subject: | Re: make == as = ? |
Date: | 2004-04-07 15:33:27 |
Message-ID: | 200404070833.27263.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fabien,
> Moreover, there are many SQL flavors around, so whatever the detailed
> syntax I learn them, it won't be the one they will have to face if the
> database they use is different. So why bother?
There are so many Java flavors around, why bother teaching the students syntax
at all? The flavor they work with in your class will probably be different
from what they have on the job.
See my point?
One of the primary reasons for the existence of international standards is
education. If you stick to Beginning & Intermediate SQL92, you can give your
students a set of SQL syntax that they can use on 80% of the RDBMSes in
service, including Postgres, HSQLDB, SQLite, Oracle, and SQL Server. This
is serving them well.
Were I teaching a class with a SQL component, using PostgreSQL as a tool, I
would be very careful to avoid letting my students use an extensions to SQL;
no "!=", no "SELECT DISTINCT ON" and no alias references in the GROUP BY
clause.
Allowing your students to use a non-standard operator that will fail them the
instant they leave the classroom is serving them badly indeed.
--
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2004-04-07 15:34:42 | Re: make == as = ? |
Previous Message | Stephan Szabo | 2004-04-07 15:13:44 | Re: make == as = ? |