From: | "Chuck McDevitt" <cmcdevitt(at)greenplum(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Gregory Stark" <stark(at)enterprisedb(dot)com> |
Cc: | "Michael Glaesemann" <grzm(at)seespotcode(dot)net>, "Ben Tilly" <btilly(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SQL feature requests |
Date: | 2007-08-23 17:16:40 |
Message-ID: | EB48EBF3B239E948AC1E3F3780CF8F880277B262@MI8NYCMAIL02.Mi8.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> > This seems like a particularly petty case compared to a lot of other
> > extensions we do allow.
>
> That's exactly the problem. Most of our other extensions are
justified
> by some significant capability gain. This isn't --- it provides zero
> new functionality, and the "convenience" factor amounts to the saving
> of
> one keystroke (ok, maybe two if you insist on a space before the
> alias).
> Pretty weak argument...
>
> regards, tom lane
>
Tom, it isn't just a case of "convenience". When we are trying to
convert users from another database (say Oracle for example) to
PostgeSQL, one of the big stumbling blocks that slows down the work is
all the little query changes that people have to make (people who might
not have written the query as well), and it can require the review of
hundreds or thousands of SQL scripts and applications. The harder it
is, the more reluctant they are to convert.
Sometimes supporting "de-facto" standards as well as official standards
makes sense.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-23 17:19:17 | Re: [COMMITTERS] pgsql: Add configure option --with-system-tzdata to use operating system |
Previous Message | Tom Lane | 2007-08-23 17:08:01 | Re: Undetected corruption of table files |