Re: [HACKERS] proposal psql \gdesc - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] proposal psql \gdesc
Date
Msg-id alpine.DEB.2.20.1706041037550.14152@lancre
Whole thread Raw
In response to Re: [HACKERS] proposal psql \gdesc  (Brent Douglas <brent.n.douglas@gmail.com>)
Responses Re: [HACKERS] proposal psql \gdesc
List pgsql-hackers
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!

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Brent Douglas
Date:
Subject: Re: [HACKERS] proposal psql \gdesc
Next
From: Erik Rijkers
Date:
Subject: Re: [HACKERS] logical replication - still unstable after all thesemonths