fix for bug #1808053. we go with numeric, which will lose precision, but can handle...

larger than int. Since reltuples is pretty fuzzy anyway, this seems like a fair balance.

diff --git a/classes/database/Postgres72.php b/classes/database/Postgres72.php
index 7ecad1b4f066063464833ed8edbcc54902f9d595..49ccd80760cd2fd4e4b24534d50b20e42e46e12e 100644 (file)
--- a/classes/database/Postgres72.php
+++ b/classes/database/Postgres72.php
@@ -4,7 +4,7 @@
  * A class that implements the DB interface for Postgres
  * Note: This class uses ADODB and returns RecordSets.
  *
- * $Id: Postgres72.php,v 1.90 2007/10/02 21:36:35 ioguix Exp $
+ * $Id: Postgres72.php,v 1.91 2007/10/18 12:29:40 xzilla Exp $
  */
 
 
@@ -205,7 +205,7 @@ class Postgres72 extends Postgres71 {
                $sql = "SELECT NULL AS nspname, c.relname, 
                                        (SELECT usename FROM pg_user u WHERE u.usesysid=c.relowner) AS relowner, 
                                        (SELECT description FROM pg_description pd WHERE c.oid=pd.objoid AND objsubid = 0) AS relcomment,
-                                       reltuples::bigint
+                                       reltuples::numeric
                         FROM pg_class c WHERE c.relkind='r' {$where}ORDER BY relname";
                return $this->selectSet($sql);
        }