Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id EF79464FD9B for ; Thu, 23 Oct 2008 16:04:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 39118-08 for ; Thu, 23 Oct 2008 16:04:52 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 5D2C364FD8D for ; Thu, 23 Oct 2008 16:04:52 -0300 (ADT) Received: from commandprompt.com (CPE001b63afe888-CM001adea9c5a6.cpe.net.cable.rogers.com [99.236.211.160]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m9NJ8trn024886 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 23 Oct 2008 12:08:58 -0700 Date: Thu, 23 Oct 2008 15:04:47 -0400 From: Andrew Sullivan To: pgsql-general@postgresql.org Subject: On standards weenies (was: Annoying Reply-To) Message-ID: <20081023190446.GO3413@commandprompt.com> Mail-Followup-To: Andrew Sullivan , pgsql-general@postgresql.org References: <200810231701.m9NH1ML21995@momjian.us> <4900B39B.2040508@kkmfg.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4900B39B.2040508@kkmfg.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Thu, 23 Oct 2008 12:08:59 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200810/1046 X-Sequence-Number: 139295 On Thu, Oct 23, 2008 at 01:25:47PM -0400, Collin Kidder wrote: > that that makes Thunderbird crippled but I see it more as a sign that > nobody outside of a few fussy RFC worshipping types would ever want the > behavior of the Postgre list. Indeed. And PostgreSQL not interpreting '' as NULL, or '2008-02-31' as a date, or other such silly strictness is just the imposition on you of the personal views of a few fussy ANSI worshipping types. Nobody would ever want such behaviour. Of course, you could consider that the behaviour as defined in the standards, which are there to ensure good interoperability, were written over many years by painstaking standards weenie types who spent a great amount of time thinking about the advantages and disadvantages of these various options.[1] Or perhaps you think that you're the only person to whom it ever occurred that some different behaviour might be desirable? Sorry, but pointing and laughing at people with whom you disagree doesn't constitute an argument. Relying on an appeal to popularity is, in fact, a well-known fallacy (sometimes known as _ad populum_). If you want to argue that the standard is wrong, you need something better than this. Alternatively, please go stand in the corner with the people who think that MySQL version 3.x is the pinnacle of correct database behaviour. A [1] To pick an example I can think of off the top of my head, you would not believe just how much wrangling has gone on this year alone over whether the "ß" character (LATIN SMALL LETTER SHARP S) should or should not be allowed into internationalized domain names. -- Andrew Sullivan ajs@commandprompt.com +1 503 667 4564 x104 http://www.commandprompt.com/