-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> P.S. The use of capital "s" is possible a source of some of the resistance. It
> seems like a lowercase "s" or something else that doesn't need multiple
> keystrokes would be a lot easier to type. Is there some limitation on the
> \command parser t
On 6/16/05, David Fetter <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 16, 2005 at 07:54:29PM -, Greg Sabino Mullane wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > I recently submitted a patch that makes all the database objects
> > behave in the same way as far as the back
On Thu, Jun 16, 2005 at 07:54:29PM -, Greg Sabino Mullane wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I recently submitted a patch that makes all the database objects
> behave in the same way as far as the backslash psql commands.
> Currently, tables work like this: \dt lis
On Thu, 16 Jun 2005, Greg Sabino Mullane wrote:
I recently submitted a patch that makes all the database objects behave
in the same way as far as the backslash psql commands. Currently, tables
work like this: \dt lists all non-system tables in your path, while
\dtS shows only the system tables.
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> I maintain that it makes more sense for those few people who regularly look
> at system functions to add a "S" than to have everyone else have to do
> things such as "\df public."
@@aol(me too).
fwiw, i think "few" may be a bit optimistic her
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I recently submitted a patch that makes all the database objects behave
in the same way as far as the backslash psql commands. Currently, tables
work like this: \dt lists all non-system tables in your path, while
\dtS shows only the system tables. Th
