Tom, Andrew, Robert,
> More to the point: how can you build a "good" interface on top of a
> "bad" one? Whatever fundamental shortcomings exist in the latter cannot
> be hidden by the former.
I think "bad" and "good" are pretty irrelevant myself. The system tables are
very "good" at what they do: support the postgresql code base. They are not
*meant* to be user-friendly. That's why we need a different "interface" to
be "good" for a different purpose. Which is what we're trying to do.
--
Josh Berkus
Aglio Database Solutions
San Francisco
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
