2010/12/17 Andrew Dunstan <and...@dunslane.net>: > > > On 12/17/2010 12:15 PM, Pavel Stehule wrote: >> >> 2010/12/17 Itagaki Takahiro<itagaki.takah...@gmail.com>: >>> >>> It should be not a main subject, but I remember there was a discussion >>> that "IN ARRAY array-expression" looks redundant for a literal array: >>> >>> IN ARRAY ARRAY[1, 3, 5] >>> >>> Are there any improvement for the issue? >> >> yes. It know it. The reason for this is bigger space for possible >> future features related to FOREACH loop. >> > > So what you're saying is we need to allow ugliness now so we can have more > ugliness in future? I don't find that a convincing argument. I share the > dislike for this syntax.
can be strange from me, but it is. If we close a back door now, then we have not a space after ten years. There can be possible loops over records, maybe over other iterable data. With this design is important one think. A keyword after K_IN must not be a reserved keyword. I am expecting, so typical use case doesn't be a iteration over constant array, but over variable so mostly often you have to write FOREACH var IN ARRAY second_var LOOP ... END LOOP Regards Pavel > > cheers > > andrew > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
