| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: poll: CHECK TRIGGER? |
| Date: | 2012-03-09 22:54:10 |
| Message-ID: | 1331333650.23681.14.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-03-09 23:00:34 | Re: poll: CHECK TRIGGER? |
| Previous Message | Tom Lane | 2012-03-09 22:44:32 | Re: NULL's support in SP-GiST |