Re: [HACKERS] proposal psql \gdesc

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: [HACKERS] proposal psql \gdesc
Дата
Msg-id CAFj8pRDrNVecPpWFTWsm+t3QKu8W1rzyjqZKeKbahkkEoHR70Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] proposal psql \gdesc  (Fabien COELHO <coelho@cri.ensmp.fr>)
Ответы Re: [HACKERS] proposal psql \gdesc  (Fabien COELHO <coelho@cri.ensmp.fr>)
Re: [HACKERS] proposal psql \gdesc  (Fabien COELHO <coelho@cri.ensmp.fr>)
Список pgsql-hackers
Hi

2017-06-04 10:47 GMT+02:00 Fabien COELHO <coelho@cri.ensmp.fr>:

Hello Brent,

Regarding the error message earlier

'No columns or command has no result',

it might be clearer with the slightly longer

'The result has no columns or the command has no result'.

I agree that a better phrasing may be possible.

I'm hesitating about this one because word "result" appears twice, but this is the underlying issue, maybe there is no result, or there is a result but it is empty... so somehow this might be unavoidable. On rereading it, I think that your sentence is better balance as the two cases have both a verb and a structured the same, so it seems better.

Another terser version could be: 'No or empty result' or 'Empty or no result', but maybe it is too terse.

I didn't read the patch though, just the email so that might not make sense in context.

Thanks for the suggestion!

new update - rebase, changed message

Regards

Pavel 



--
Fabien.

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Amit Langote
Дата:
Сообщение: Re: [HACKERS] BEFORE trigger can cause undetected partitionconstraint violation
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: [HACKERS] UPDATE of partition key