From: | "ktm(at)rice(dot)edu" <ktm(at)rice(dot)edu> |
---|---|
To: | Rafael Martinez Guerrero <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, "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:27:13 |
Message-ID: | 20140206152713.GD26514@aart.rice.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 06, 2014 at 04:21:41PM +0100, Rafael Martinez Guerrero wrote:
> 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
>
Hi Rafael,
It sounds like a bug in the XDB trigger generation code. Maybe file a bug
report.
Regards,
Ken
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2014-02-06 15:32:51 | Re: extension_control_path |
Previous Message | Andres Freund | 2014-02-06 15:26:45 | Re: updated emacs configuration |