Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id AAA87266 for ; Sat, 27 May 2000 00:07:15 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id AAA15148; Sat, 27 May 2000 00:06:54 -0400 (EDT) To: Mike Mascari cc: Bruce Momjian , pgsql-hackers@postgresql.org Subject: Re: Re: [SQL] aliases break my query In-reply-to: <392F28A3.7EB67B84@mascari.com> References: <200005262343.TAA02242@candle.pha.pa.us> <392F28A3.7EB67B84@mascari.com> Comments: In-reply-to Mike Mascari message dated "Fri, 26 May 2000 21:45:07 -0400" Date: Sat, 27 May 2000 00:06:54 -0400 Message-ID: <15145.959400414@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200005/713 Mike Mascari writes: > How about a SET variable which allows PostgreSQL to reject any > queries which are not entirely within the specificaton; kind of > like -ansi -pedantic with gcc? Perhaps that's quite a bit of > work, but it seems quite valuable for developing portable > applications...Of course dependency on PostgreSQL extensions > isn't a bad thing either ;-) Hmm. Some aspects of that seem fairly straightforward, like rejecting the table-not-in-FROM extension being discussed here. On the other hand, it'd be painful to check for uses of datatypes or functions not present in the standard. In any case, I think the general reaction will be "good idea but a huge amount of work compared to the reward". Unless someone steps forward who's willing to do the work, I'd bet this won't happen... regards, tom lane