On 09/28/2015 06:33 AM, Michael Paquier wrote:
> On Sun, Sep 27, 2015 at 11:27 AM, Amir Rohan wrote:
>> Further editing. See attached V3.
>
> I think that you should consider adding this patch to the next commit
> fest so as we do not lose track of it:
> https://commit
On 09/26/2015 12:02 PM, Amir Rohan wrote:
> Hi all,
>
> See attached changed to current docs on subject. They have clearly
> been reworked by multiple people piecemeal and had many issues
> which made less than a joy to read, in fact they were damn frustrating
> to read.
Fu
On 09/26/2015 12:02 PM, Amir Rohan wrote:
> Hi all,
>
> See attached changed to current docs on subject. They have clearly
> been reworked by multiple people piecemeal and had many issues
> which made less than a joy to read, in fact they were damn frustrating
> to read.
Upd
Hi all,
See attached changed to current docs on subject. They have clearly
been reworked by multiple people piecemeal and had many issues
which made less than a joy to read, in fact they were damn frustrating
to read.
I've gone through the whole section and rewritten what needed to be.
I think th
On Monday, September 21, 2015, David G. Johnston wrote:
>To be honest, if you have a situation where you think you need to alias "*"
>you should probably be expanding that "*" out into individual column names
>anyway, which you can easily alias.
>
That depends. If my table has 30 columns and I j
On Monday, September 21, 2015, Amir Rohan wrote:
>> From
>> http://www.postgresql.org/docs/9.4/static/sql-select.html[http://www.postgresql.org/docs/9.4/static/sql->>
>> select.html] (and previous version too):
>>
>> ##SELECT List
>>
>>
From http://www.postgresql.org/docs/9.4/static/sql-select.html (and previous version too):
##SELECT List
<...>
Instead of an _expression_, * can be written in the output list as a shorthand for all the columns of the selected rows.
Also, you can write table_name.* as a shorth
