X-Original-To: pgsql-hackers@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id E282C475C15 for ; Wed, 23 Apr 2003 00:40:53 -0400 (EDT) Received: from trolak.mydnsbox2.com (ns1.mydnsbox2.com [207.44.142.118]) by postgresql.org (Postfix) with ESMTP id 222BA475A45 for ; Wed, 23 Apr 2003 00:40:53 -0400 (EDT) Received: from DUNSLANE (cpe-024-211-132-214.nc.rr.com [24.211.132.214]) (authenticated (0 bits)) by trolak.mydnsbox2.com (8.11.6/8.11.6) with ESMTP id h3N4WpL27344 for ; Tue, 22 Apr 2003 23:32:51 -0500 Message-ID: <001c01c30952$890face0$6401a8c0@DUNSLANE> From: "Andrew Dunstan" To: "PostgreSQL Hackers" References: Subject: Re: Are we losing momentum? Date: Wed, 23 Apr 2003 00:40:58 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Status: No, hits=-19.1 required=5.0 tests=BAYES_20,ORIGINAL_MESSAGE,QUOTED_EMAIL_TEXT,REFERENCES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/802 X-Sequence-Number: 38292 ----- Original Message ----- From: "Dann Corbit" > One of the major reasons for reporting servers is that people who do not > understand the data (or even SQL very well) will often cause great > problems in ad-hoc query situations. > > Those performing the queries typically do not understand the data very > well. This is especially true in a database with hundreds or thousands > of tables. Usually, they will have a pretty good understanding of a > small subset of the tables that contain the information that they are > after, but even that is not always true. > *nod* This is something to be addressed by policy rather than technology, I suspect. One large and famous financial institution I worked at had a simple policy regarding production DBs: all client access was to be through stored procedures. This was enforced by the DB's own privileges system - only the SPs were visible, and they could only be installed by the database group. This also forced the developers to abstract the DB access into a separate layer, so that when it was productised only that layer needed to be changed (this is a Good Thing (tm)). andrew