Re: psql line number reporting from stdin
От | Gurjeet Singh |
---|---|
Тема | Re: psql line number reporting from stdin |
Дата | |
Msg-id | CABwTF4X67wZvZp7y80zErE41bVb6aE5o29M=6trK4ZArFTGSqw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: psql line number reporting from stdin (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: psql line number reporting from stdin
|
Список | pgsql-hackers |
On Mon, Nov 28, 2011 at 8:10 AM, Robert Haas <robertmhaas@gmail.com> wrote:
Seems like a good idea to me.On Sat, Nov 26, 2011 at 3:36 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> There is a long-standing oddity in psql that running
>
> psql -f foo.sql
>
> returns error messages with file name and line number, like
>
> psql:foo.sql:1: ERROR: syntax error at or near "foo"
>
> but running
>
> psql < foo.sql does not. I suggest we change the latter to print
>
> psql:<stdin>:1: ERROR: syntax error at or near "foo"
>
> Other examples for the use of the spelling "<stdin>" in this context
> include gcc and slonik.
>
> Error messages printed in interactive mode will not be affected, of
> course.
>
> Patch attached.
Naysayers can always make a case for backwards-compatibility, or not breaking the scripts written with the existing behaviour in mind. Do our docs have anything to say about scripts executed from stdin?
--
Gurjeet Singh
EnterpriseDB Corporation
The Enterprise PostgreSQL Company
EnterpriseDB Corporation
The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: