Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Could we have a way to turn this off? At least for functions and
operators? For my usage, at least, this will be a serious step
backwards in usefulness
But all we are
Greg Sabino Mullane wrote:
But all we are asking is that you add a single letter ('S') to your
queries. There are probably only a handful of people besides yourself
who use \df to look up system functions, while the other 99% of the
world would benefit greatly from being able to do a \df and
On Friday 27 May 2005 20:45, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
On Fri, May 27, 2005 at 04:16:15PM -0400, Tom Lane wrote:
There seems to be a distinct lack of unanimity about that judgment ;-)
Well, yes, _across Postgres hackers_. But if we were to ask
Robert Treat [EMAIL PROTECTED] writes:
I'm not against the idea of a config variable, but this is what, the
third or fourth go around on this? It seems rather unfair to put this
burden upon the current patch writer at this stage of the game...
The fact that objections keep being raised should
On Saturday 28 May 2005 11:12, Tom Lane wrote:
Robert Treat [EMAIL PROTECTED] writes:
I'm not against the idea of a config variable, but this is what, the
third or fourth go around on this? It seems rather unfair to put this
burden upon the current patch writer at this stage of the game...
Tom Lane wrote:
Greg Sabino Mullane [EMAIL PROTECTED] writes:
Attached is my backslash consistency patch which basically makes
all the backslash commands behave as \dt does: \d* shows non-system
objects, and \d*S shows system objects.
Could we have a way to turn this off? At least for
On Fri, 2005-05-27 at 03:45, Peter Eisentraut wrote:
Tom Lane wrote:
Greg Sabino Mullane [EMAIL PROTECTED] writes:
Attached is my backslash consistency patch which basically makes
all the backslash commands behave as \dt does: \d* shows non-system
objects, and \d*S shows system
Robert Treat [EMAIL PROTECTED] writes:
Do you have an implementation in mind? I'm having trouble coming up with
a way to do it cleanly.
A psql \set variable to choose the behavior seems like a reasonable
compromise. Perhaps it could list the \d commands that should include
system objects by
Peter Eisentraut wrote:
Robert Treat wrote:
I see hardly any use case for showing only user-defined functions
or types by default. I think consistency is not necessarily
desirable here.
See the archives for previous discussion and/or use cases.
I didn't find any. Nevertheless,
On Friday 27 May 2005 15:09, Peter Eisentraut wrote:
Robert Treat wrote:
I see hardly any use case for showing only user-defined functions
or types by default. I think consistency is not necessarily
desirable here.
See the archives for previous discussion and/or use cases.
I
On Fri, May 27, 2005 at 04:16:15PM -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
How about a psql config option? It should default to show only
non-system objects, as that is the most generally useful behavior.
There seems to be a distinct lack of unanimity about that
Robert Treat [EMAIL PROTECTED] writes:
On Friday 27 May 2005 15:09, Peter Eisentraut wrote:
I didn't find any. Nevertheless, while there are undoubtedly some uses
for everything, making this the default behavior does not seem
acceptable.
ISTM it is more acceptable than you're willing to
Alvaro Herrera [EMAIL PROTECTED] writes:
On Fri, May 27, 2005 at 04:16:15PM -0400, Tom Lane wrote:
There seems to be a distinct lack of unanimity about that judgment ;-)
Well, yes, _across Postgres hackers_. But if we were to ask
pgsql-general I have a feeling we would measure more weight on
Greg Sabino Mullane [EMAIL PROTECTED] writes:
Attached is my backslash consistency patch which basically makes all
the backslash commands behave as \dt does: \d* shows non-system objects,
and \d*S shows system objects.
Could we have a way to turn this off? At least for functions and
14 matches
Mail list logo
