Re: Common Table Expressions (WITH RECURSIVE) patch - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Common Table Expressions (WITH RECURSIVE) patch
Date
Msg-id 603c8f070809170512p64f24064u22a78a6c3a43b103@mail.gmail.com
Whole thread Raw
In response to Re: Common Table Expressions (WITH RECURSIVE) patch  ("Pavel Stehule" <pavel.stehule@gmail.com>)
Responses Re: Common Table Expressions (WITH RECURSIVE) patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> I am not sure, if these rule is good. Somebody who develop on
> postgresql should have a problems when they will be port to other
> databases in future. Reserved words in standards should be respected.

I disagree.  I have never ported an app written for PostgreSQL to
another database system, and have no plans to start.  The fact that
some other database system might barf on a particular bit of SQL is
insufficient reason for PostgreSQL to do the same thing.

If people want to write code that will work on multiple databases,
they should of course avoid using any SQL reserved words for anything
other than their reserved purposes.  But there is no reason for the
database system to unilaterally shove that down everyone's throat.  It
is very easy to overdo the idea of protecting users from themselves.

...Robert


pgsql-hackers by date:

Previous
From: Andrew Chernow
Date:
Subject: Re: [PATCHES] libpq events patch (with sgml docs)
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] libpq events patch (with sgml docs)