X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id CFB7F9FA5DD for ; Fri, 9 Jun 2006 16:34:05 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 79063-02 for ; Fri, 9 Jun 2006 16:34:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 0BF2C9FA1A8 for ; Fri, 9 Jun 2006 16:34:00 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 9153356480; Fri, 9 Jun 2006 14:33:57 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Fri, 9 Jun 2006 14:33:57 -0500 Date: Fri, 9 Jun 2006 14:33:57 -0500 From: "Jim C. Nasby" To: pgsql-hackers@postgresql.org Subject: List schema contents Message-ID: <20060609193356.GC57289@pervasive.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060609:pgsql-hackers@postgresql.org::VUHPcnNUdYVaDd1N:000000000 0000000000000000000000002Xrt X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/461 X-Sequence-Number: 84694 Currently, the only way to get a listing of tables in a schema via psql is to modify your search_path, which is both non-intuitive and a PITA. You can do \d schemaname., but that's the equivalent of set search_path = schemaname \d * I'd like to propose that the behavior of \d schemaname. be changed to match set search_path = schemaname \d That avoids issues with table name conflicts that could arise if the trailing . wasn't required. And the old behavior is still available as \d schemaname.* One problem I see is that this will break the ability to search for tablename. via regex. Since that's easy to do via tablename?, I don't think it's a big deal, unless someone has better ideas on how to indicate we want to list something for a specific schema. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461