Received: from mx99.openu.ac.il (arbel.openu.ac.il [147.233.32.4]) by hub.org (8.9.3/8.9.3) with ESMTP id FAA29630 for ; Wed, 2 Jun 1999 05:33:59 -0400 (EDT) (envelope-from herouth@oumail.openu.ac.il) Received: from talmon.openu.ac.il (talmon.openu.ac.il [147.233.32.11]) by mx99.openu.ac.il (Postfix) with ESMTP for id 0F0E74B5D6; Wed, 2 Jun 1999 12:33:57 +0300 (IDT) Received: from [147.233.159.109] (mac-herouth.pc.openu.ac.il) by talmon.openu.ac.il (Netscape Messaging Server 3.54) with ESMTP id AAA6D7F; Wed, 2 Jun 1999 12:36:29 +0300 X-Sender: herouth@shaked.cc.openu.ac.il Message-Id: In-Reply-To: <000d01beac91$92bdf2f0$0c01a8c0@quay> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 2 Jun 1999 12:34:42 +0300 To: "Michael Yeung" , "pgsql SQL" From: Herouth Maoz Subject: Re: [SQL] Order by At 03:48 +0300 on 02/06/1999, Michael Yeung wrote: > Hi all, > > Is anyone know that if we allow order-by clause in the view structure. > If not, how can we take the ordering of the UNION ALL in 2 different bags ? Correct me if I'm wrong, but ORDER BY shoud not be part of a view, in the same way it is not a part of a table. A table is defined as an unordered collection of tuples. In any given query, you can define the order of the tuples returned. But the table itself is not ordered. A view should look to the user just like a table. The order of the tuples is part of the query, not part of the table, and not part of the view. Herouth -- Herouth Maoz, Internet developer. Open University of Israel - Telem project http://telem.openu.ac.il/~herutma