http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DBAL-76 Doctrine DBAL <p>The Postgres Schema code is very hard to read and inconsistent across the board. Some use pg_class, some pg_tables. Namespaces /Schema are not always properly checked for. There should be a really unified way on how to approach schema query issues.</p> DBAL-76

PostgreSQL Platform list* SQL code is in need of serious love

Improvement Major Open Unresolved Benjamin Eberlei Benjamin Eberlei Sun, 12 Dec 2010 08:08:01 +0000 Wed, 8 Jun 2011 17:05:08 +0000 0 1 <p>I'm not sure what this ticket is about exactly, but...</p> <p>"Namespaces /Schema are not always properly checked for."</p> <p>Usually, one would not want to specify them and set the search_path instead. Or are you meaning the schema analysis queries used internally? (If so, yes, it kind of sucks in that case, but note that there are a bunch of *_is_visible() methods, e.g. pg_catalog.pg_table_is_visible(rel.oid) which will strip out invisible schemas directly. This may be simpler than injecting schema references all over the place in that it also processes permissions.)</p> <p>Also, note that PG has a whole bunch of pg_catalog views, which are available in the information_schema.</p>