On fre, 2012-03-09 at 21:54 +0100, Pavel Stehule wrote:
> no, you can check any PL language - and output result is based on SQL
> Errors, so it should be enough for all PL too.
But then I would have to map all language-specific error reports to some
SQL error scheme, which is not only cumbersome but pretty useless. For
example, a Python programmer will be familiar with the typical output
that pylint produces and how to fix it. If we hide that output behind
the layer of SQL-ness, that won't make things easier to anyone.