Re: [PATCH] parser: optionally warn about missing AS for column and table aliases

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Marko Tiikkaja <marko(at)joh(dot)to>
Cc: Oskari Saarenmaa <os(at)ohmu(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] parser: optionally warn about missing AS for column and table aliases
Date: 2014-09-05 21:11:53
Message-ID: CAFj8pRDutFHoxn=Eo9WHevtRrzih_OhuoPA0cwZ0evKTbhVLzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2014-09-05 23:06 GMT+02:00 Marko Tiikkaja <marko(at)joh(dot)to>:

> On 2014-09-05 22:56, Oskari Saarenmaa wrote:
>
>> What'd be a good name for the GUC controlling this,
>> missing_column_as_warning?
>>
>
> I don't know about others, but I've previously had the idea of having more
> warnings like this (my go-to example is DELETE FROM foo WHERE bar IN
> (SELECT bar FROM barlesstable); where "barlesstable" doesn't have a column
> "bar"). Perhaps it would be better to have a guc with a list of warnings,
> similarly to what we did for plpgsql.extra_warnings?
>
> Now that I start thinking about it, more ideas for such warnings start
> springing up..
>

I had same idea - maybe some general mode "prune human errors" mode

Pavel

>
>
> .marko
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oskari Saarenmaa 2014-09-05 21:12:35 Re: [PATCH] Filter error log statements by sqlstate
Previous Message Marko Tiikkaja 2014-09-05 21:06:50 Re: [PATCH] parser: optionally warn about missing AS for column and table aliases