Received: from thor.tht.net (thor.tht.net [209.47.145.4]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eB6Da0t17102 for ; Wed, 6 Dec 2000 08:36:00 -0500 (EST) (envelope-from edmar@brasmap.com) Received: from gw.acate.com.br ([200.215.17.89]) by thor.tht.net (8.9.3/8.9.3) with ESMTP id IAA71958 for ; Wed, 6 Dec 2000 08:43:34 GMT (envelope-from edmar@brasmap.com) Received: from ana ([192.168.1.13]) by gw.acate.com.br (8.9.3/8.9.3) with SMTP id KAA12855 for ; Wed, 6 Dec 2000 10:43:12 -0200 From: "Edmar Wiggers" To: Subject: RE: Using SELECT as DDL/DML statement is wrong (was RE: reinitialize a sequence?) Date: Wed, 6 Dec 2000 10:43:59 -0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <7F124BC48D56D411812500D0B747251480F315@fileserver002.intecsystems.co.uk> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Archive-Number: 200012/37 X-Sequence-Number: 368 > But, altering the database in a procedure > called from a select is a design decision, > and if somebody wants to do it, well, it's > their problem. There may (on very few > occasions, one would hope) actually be some > good reasons to do this. Ok, it's their problem. But, as a DBA, I would like to have stored procedures. Having that, I would also like a way to prevent any application development that uses SELECT statements to alter the database. By definition, that's not what SELECT is for (and so it is bad practice to use it that way). Currently however, that's the only whay to do it (use something similar to stored procs). And, true, that's much better than not doing it at all. Yours sincerely, Edmar Wiggers BRASMAP Information Systems +55 48 9960 2752