| From: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
|---|---|
| To: | Daniel Farina <daniel(at)heroku(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "on existing update" construct |
| Date: | 2013-05-15 21:22:11 |
| Message-ID: | CALSLE1N8R0VDHF=c-Sm11GObe=+jeBXQuVdRoHP-DEhfzMHo2g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Well ya, stored procedure also was thinking about pre-insert trigger.
Am sure folks here must have gone thru this and had alternatives. Also was
reading about merge_by_key.
On Wed, May 15, 2013 at 12:51 PM, Daniel Farina <daniel(at)heroku(dot)com> wrote:
> On Wed, May 15, 2013 at 11:44 AM, Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com>
> wrote:
> > Hello,
> >
> > Is there an alternative of Sybase "on existing update" construct in
> pgsql.
> >
> > "ON DUPLICATE KEY UPDATE" doesn't work.
> >
> > Thanks in advance!
>
> No, you'll have to either handle this in the application or use a
> stored procedure at this time. The omission of such a construct from
> psql's "\h" command and the manual is not in error.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jon Nelson | 2013-05-15 21:26:15 | Re: fallocate / posix_fallocate for new WAL file creation (etc...) |
| Previous Message | Robert Haas | 2013-05-15 21:18:06 | Re: Heap truncation without AccessExclusiveLock (9.4) |