| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | chris travers <chris(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: PL/PgSQL strict_mode |
| Date: | 2013-09-14 09:26:16 |
| Message-ID: | 52342BB8.4040506@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14/09/2013 06:53, chris travers wrote:
> I am going to suggest that STRICT is semantically pretty far from what is meant
> here in common speech. I think STRICT here would be confusing. This would be
> really pretty severe for people coming from Perl or MySQL backgrounds.
The name of the feature doesn't really matter. I chose STRICT because
the behaviour is somewhat similar to INTO .. STRICT.
> May I suggest SINGLE as a key word instead? It might be worth having attached
> to a INSERT, UPDATE, and DELETE statements.
I already suggested the "attach a keyword to every statement" approach,
and got shot down quite quickly.
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | samthakur74 | 2013-09-14 10:51:06 | Re: pg_stat_statements: calls under-estimation propagation |
| Previous Message | Greg Stark | 2013-09-14 08:57:43 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |