| From: | Rafael Martinez Guerrero <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: open and close columns in the NEW record not allowed |
| Date: | 2014-02-06 15:21:41 |
| Message-ID: | 1391700101.10585.4.camel@drop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2014-02-06 at 07:11 -0800, Adrian Klaver wrote:
> On 02/06/2014 06:35 AM, Rafael Martinez Guerrero wrote:
> > We think the behavior should be consistent, either it is allow to use
> > them or not, but not like it is today.
> >
>
> " As a general rule, if you get spurious parser errors for commands that
> contain any of the listed key words as an identifier you should try to
> quote the identifier to see if the problem goes away."
>
>
> Which indeed solves the problem on my end at least:
>
Hello
Thanks for the feedback.
Our problem is that an application decides the name of the columns in
the tables and "XDB replication" from EnterpriseDB decides the triggers.
We have no control over the code :-(
regards,
--
Rafael Martinez Guerrero
Center for Information Technology Services
University of Oslo, Norway
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-06 15:24:34 | Re: updated emacs configuration |
| Previous Message | Andres Freund | 2014-02-06 15:21:02 | Re: updated emacs configuration |