Received: from trends.net (root@clio.trends.ca [209.47.148.2]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA01508 for ; Sun, 13 Jun 1999 13:25:17 -0400 (EDT) (envelope-from bmccoy@access1.lan2wan.com) Received: from access1.lan2wan.com (bmccoy@access1.lan2wan.com [205.177.8.10]) by trends.net (8.8.8/8.8.8) with ESMTP id MAA13812 for ; Sun, 13 Jun 1999 12:49:55 -0400 (EDT) Received: (from bmccoy@localhost) by access1.lan2wan.com (8.8.5/) id QAA11097; Sun, 13 Jun 1999 16:15:37 -0400 (EDT) Date: Sun, 13 Jun 1999 16:15:37 -0400 (EDT) From: "Brett W. McCoy" To: pgsql-sql@postgreSQL.org Subject: DISTINCT not working Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have this view that is based upon selecting distinct values of a column and providing the count of rows for that distinct value. It is being used in an application so that when it is started (via a web browser), various statistics about the database are shown. This has been working fine for about 2 months, but suddenly, on Friday, the view stopped working, it returns a single row with an empty value and a 0 count. If I do a direct SQL statement to pull out the distinct values frm the base table, it also returns a single row. The values are there, as there are over 100,000 rows in the table, and there should be about 6 distinct values for the column in question. I tried reindexing, vaccuming, and everything, but cannot figure out why any statements selecting distinct values on this table aren't working. Why would this happen? Has something gotten corrupted? Brett W. McCoy http://www.lan2wan.com/~bmccoy ----------------------------------------------------------------------- Look, we play the Star Spangled Banner before every game. You want us to pay income taxes, too? -- Bill Veeck, Chicago White Sox