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 eA5I97s37819 for ; Sun, 5 Nov 2000 13:09:11 -0500 (EST) (envelope-from depesz@gruby.cs.net.pl) Received: from gruby_int.cs.net.pl (cafe1.rem.pl [195.205.133.61]) by thor.tht.net (8.9.3/8.9.3) with ESMTP id JAA27195 for ; Sun, 5 Nov 2000 09:06:59 GMT (envelope-from depesz@gruby.cs.net.pl) Received: (from localhost user: 'depesz' uid#500 fake: STDIN (depesz@gruby.cs.net.pl)) by gruby.cs.net.pl id ; Sun, 5 Nov 2000 12:44:36 +0100 Date: Sun, 5 Nov 2000 12:44:36 +0100 From: hubert depesz lubaczewski To: pgSQL Subject: Question about ordering views Message-ID: <20001105124436.B27532@gruby> Reply-To: depesz@depesz.pl Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i X-Archive-Number: 200011/32 X-Sequence-Number: 63 Hi, I'm wondering if it is possible to make view (or procedure or triger or rule or something) to force SELECTs to this view (rule, procedure or something) to force always using predefined ORDER BY statement without removing possibility to use WHERE statement to this SELECT. regards, depesz -- hubert depesz lubaczewski ------------------------------------------------------------------------ najwspanialszą rzeczą jaką dało nam nowoczesne społeczeństwo,