| From: | Dennis Gearon <gearond(at)fireserve(dot)net> |
|---|---|
| To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
| Cc: | Edmund Dengler <edmundd(at)eSentire(dot)com>, Philip Boonzaaier <phil(at)cks(dot)co(dot)za>, Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Bulk Insert / Update / Delete |
| Date: | 2003-08-21 17:35:30 |
| Message-ID: | 3F4502E2.6020601@fireserve.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I take it, following this thread, is that REPLACE is not in the SQL
standard?
Bruno Wolff III wrote:
>On Thu, Aug 21, 2003 at 12:56:18 -0400,
> Edmund Dengler <edmundd(at)eSentire(dot)com> wrote:
>
>
>>Wasn't there a feature in some SQL database which was the equivalent of
>>UPDATE OR INSERT ... based on the primary key? Would this accomplish what
>>you want (I know that I have a desire for this feature a couple of times,
>>as I simply have code or triggers to essentially do the equivalent)? Is
>>this a desirable feature for Postgresql?
>>
>>
>
>I remember people asking for the equivalent of MYSQL's REPLACE command
>in previous threads.
>
>Another alternative is allowing the clients to determine what do do after an
>error so that you could try an insert first and then do an update if it
>failed without aborting your transaction.
>
>---------------------------(end of broadcast)---------------------------
>TIP 7: don't forget to increase your free space map settings
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Tocci | 2003-08-21 17:50:01 | Looking for dependent object DROP and CREATE scripts |
| Previous Message | Bruno Wolff III | 2003-08-21 17:31:18 | Re: Bulk Insert / Update / Delete |