Received: from dune.krs.ru (dune.krs.ru [195.161.16.38]) by hub.org (8.9.1/8.9.1) with ESMTP id FAA13054; Tue, 24 Nov 1998 05:35:57 -0500 (EST) (envelope-from vadim@krs.ru) Received: from krs.ru (localhost.krs.ru [127.0.0.1]) by dune.krs.ru (8.8.8/8.8.7) with ESMTP id RAA21934; Tue, 24 Nov 1998 17:33:31 +0700 (KRS) (envelope-from vadim@krs.ru) Sender: root@dune.krs.ru Message-ID: <365A8B79.31DC53FA@krs.ru> Date: Tue, 24 Nov 1998 17:33:29 +0700 From: Vadim Mikheev Organization: OJSC Rostelecom (Krasnoyarsk) X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Jan Wieck CC: s-fery@kkt.sote.hu, pgsql-sql@postgreSQL.org, hackers@postgreSQL.org Subject: Re: [SQL] cursor and update + view References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jan Wieck wrote: > > > My other problem is with the views: it seems not work if there is an > > aggregate command in the SELECT. It's only my experience, or others > > noticed it also? (The details are on the pgsql-novice (subject: view > > and aggregate command problem)) > > Aggregates in view's are still buggy. It is possible to > change the grouping when doing a join from such a view and > another relation in a way, that crashes the backend. We'll have to implement subqueries in FROM someday - this would allow handle aggregates in views... Vadim