Re: BUG #8893: Precompiler ECPG doesn't check Var-List in Select corrrect. - Mailing list pgsql-bugs

From Boszormenyi Zoltan
Subject Re: BUG #8893: Precompiler ECPG doesn't check Var-List in Select corrrect.
Date
Msg-id 52DDA126.8040003@pr.hu
Whole thread Raw
In response to Re: BUG #8893: Precompiler ECPG doesn't check Var-List in Select corrrect.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #8893: Precompiler ECPG doesn't check Var-List in Select corrrect.
Re: BUG #8893: Precompiler ECPG doesn't check Var-List in Select corrrect.
List pgsql-bugs
2014-01-20 16:36 keltezéssel, Tom Lane írta:
> herbert.grohmann@vallourec.com writes:
>>         EXEC SQL SELECT
>> ...
>>             sugru_1,sugru_2,sugru_3,sugru_4,sugru_5,sugru_6,sugru_7,sugru_8,sugru_9
>> stoerzeit_a11,stoerzeit_a12,stoerzeit_a13,stoerzeit_a14,stoerzeit_a15,stoerzeit_a16
>> ...
>> Missing Komma after sugru_9 does not produce a Compiler Error!
> Unfortunately, that's legal SQL syntax: stoerzeit_a11 is taken as a column
> alias for sugru_9, even without AS in front of it.
>
> This might not be the single worst syntax choice the SQL standards
> committee ever made, but it's certainly in the running for that
> distinction.  Unfortunately, we're pretty much stuck with it :-( --- even
> if we didn't want to follow the standard as best we can, there is a whole
> lot of SQL code out there that depends on being able to omit AS.

Still, this particular problem may be caught by the preprocessor.
The SELECT targetlist is not "*", so the number of members for both
the targetlist and the user structure (INTO :s_schichtsatz) are known.

Best regards,
Zoltán Böszörményi

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] surprising to_timestamp behavior
Next
From: mlipchuk@redhat.com
Date:
Subject: BUG #8880: no indication of value when exceeded maximum length