On Sunday, June 21, 2020, Guy Burgess wrote:
>
> a.id, a.title, b.id, b.title
You are missing some double-quotes there.
Of course, this can be achieved by avoiding the (often frowned-upon) SELECT
> * syntax in the first place and using explicit column names,
Or choose better, distinguishi
On 22/06/2020 3:25 pm, Laurenz Albe wrote:
Then there is the case of "a JOIN b USING (somecol)".
Here, "somecol" will appear in the output only once. How should it be
labeled? If you say "not at all", then what do you want to happen for
SELECT * FROM a JOIN b USING (id) JOIN c USING (x)
wh
On Mon, 2020-06-22 at 14:16 +1200, Guy Burgess wrote:
> I've seen some situations where it would be very handy if PostgreSQL
> could automatically prefix column names in a SELECT query with their
> table names (or its alias). So for two tables, a & b, each with
> columns "id" and "title":
>
>
Hello,
I've seen some situations where it would be very handy if PostgreSQL
could automatically prefix column names in a SELECT query with their
table names (or its alias). So for two tables, a & b, each with
columns "id" and "title":
SELECT * FROM a , b;
instead of returning ambiguou
