Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZeTRR-0001kK-Dh for pgsql-docs@arkaria.postgresql.org; Tue, 22 Sep 2015 19:41:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZeTRQ-00070f-V6 for pgsql-docs@arkaria.postgresql.org; Tue, 22 Sep 2015 19:41:29 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZeTR5-0006d2-QL for pgsql-docs@postgresql.org; Tue, 22 Sep 2015 19:41:07 +0000 Received: from mout.gmx.com ([74.208.4.200]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.84) (envelope-from ) id 1ZeTQz-0005HO-8p for pgsql-docs@postgresql.org; Tue, 22 Sep 2015 19:41:06 +0000 Received: from [5.102.207.29] by 3capp-mailcom-lxa05.server.lan (via HTTP); Tue, 22 Sep 2015 21:40:58 +0200 MIME-Version: 1.0 Message-ID: From: "Amir Rohan" To: "David G. Johnston" Cc: "pgsql-docs@postgresql.org" Subject: Re: Docs claim that "select myTable.*" wildcard won't let you assign column names Content-Type: text/plain; charset=UTF-8 Date: Tue, 22 Sep 2015 21:40:58 +0200 Importance: normal Sensitivity: Normal In-Reply-To: References: , X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K0:kPbIq3b+OAQ6AjyOcMXyYqU5IKrsbSiWNwUSJ+IoDpi u1v7Z2ieCi4Tzi1pqiGOD2efLQ7cNq4XtYMipGUBHlpKa7XkuJ K6JjibK8xolx5hFM2vZ1QIilYwkaj/GazDQom6yUJJr+ChWdU0 /2vkmnryiMh3tQh1kzG0NiRZ3FJvO0i9gM7HQVEUYZv8Br5+4S caxMAttHzxb1lonKiVVHNvDKu2WHNV+WcWIFW38aGLHtSNcfzK Xah4X3TxoeLX48BrD63DkDZeipOpCkmKY+dgO3bkaqQdLe7W5g XMbnUjET6aPqIdayYkwx8JftOgi X-UI-Out-Filterresults: notjunk:1;V01:K0:twxsvtLhvbQ=:XUhYxBs5tjt1h8+sMnm++C bw1jyC6Dn1uAOmFkS0yp9gkGiLlvw5siiFfu3TSWYZqODeLC+V8JPVEJYxg28Sjn8XEpdwrYD Lx4v/W2Kkw01LeknCjytTG+AAw0G8lUiNF9bNZaLMvc6TOmdI64ThETI0cm6UIzR9qIjTBsF9 T36Ki16VMpYZRMr19e+eTrDPYtqRRo9NLfBo6GdIaMJLJwayfv2dXaJlZ5ygbxAdj/X7Zw8K4 qQN4C81fUCEbYvSdGL+ZnUSmQwk8m7czu/wHROGPSheCqrJbKYtcK1jIEyVfYgCukSs/sdLuQ RqqDrcrLn6l+vGZeiZpOu2ZjNGHqUPqLJpKM6yY2oxlLaNdpzIWqQLcNKH38phM4AUA6qIi6h novXt0VEpf05J4AdqVDsrqmPsSq9qO2Tqjw51b6xGgfqVECJmzmfQbXKe/KXDJIdjhw2c+rRE Mdt7GNE6+g== X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org 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 just need to rename the first couple, then I probably would find that advice unreasonable. >The docs don't make a big deal of alising other than noting individually >where they can happen (cte, from clause, select-list) and few questions >that are raised are probably better served to be simply handled on these >lists than cluttering the docs. What constitutes "clutter", or what is "obvious", really depends on who is making the assertion. A pg veteran's views probably don't mirrort those of the person you'd typically find actually reading the docs, trying to figure out how to write the query they want. But yeah, the pg documentation isn't the best resource to pick up SQL from (nor is is their purpose), and no patch I'd submit would really change that. So, we're done. Amir -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs