>>>>> "Pavel" == Pavel Stehule <pavel.steh...@gmail.com> writes:
>> Well now I feel dumb... >> >> It would be very useful if we had some way to warn users about stuff >> like this. Emitting a NOTICE comes to mind. Pavel> This can be valid query It can be, but it essentially never is. The cases where you genuinely want a correlated IN query are rare, but even then there would be something in the targetlist that referenced the inner query. The easy to catch case, I think, is when the targetlist of the IN or NOT IN subquery contains vars of the outer query level but no vars of the inner one and no volatile functions. This can be checked for with a handful of lines in the parser or a couple of dozen lines in a plugin module (though one would have to invent an error code, none of the existing WARNING sqlstates would do). Maybe David Fetter's suggested module for catching missing WHERE clauses could be expanded into a more general SQL-'Lint' module? -- Andrew (irc:RhodiumToad) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
