Re: Suggestion for psql command interpretation

From: Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>
To: Colin Wetherbee <cww(at)denterprises(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL <pgsql-general(at)postgresql(dot)org>
Subject: Re: Suggestion for psql command interpretation
Date: 2008-04-16 18:01:11
Message-ID: 200804161806.m3GI6QEj097931@smtp5.jaring.my
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

At 04:46 AM 4/16/2008, Colin Wetherbee wrote:
>Tom Lane wrote:
>>Colin Wetherbee <cww(at)denterprises(dot)org> writes:
>>>I just thought I'd report it here in case it wasn't supposed to
>>>happen, but from what you say, it seems like it's a "feature".
>>Well, it's more of a historical hangover. Personally I'd not have
>>much problem with breaking backward compatibility on this point.
>
>I'm not generally in the habit of making typos, so this doesn't
>affect me too much.
>
>However, IMHO and as I mentioned previously, I don't think
>"\timimng" should succeed. I'll leave the rest of the discussion up
>to you and the other developers, though. :)

I too agree that \timimng should not work.

Maybe someone can think of an undesirable surprise that springs from
this "feature" ;).

\i
\e

Are possible candidates (probably others could clobber files given a typo).

I think requiring a space between command and arguments would be a
good idea. And not doing stuff if there are syntax errors...

Link.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2008-04-16 18:48:17 Re: table as log (multiple writers and readers)
Previous Message Sam Mason 2008-04-16 17:59:12 Re: generate_series woes