From: | "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Cristian Prieto <cristian(at)clickdiario(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Insert Ignore or something similar... |
Date: | 2005-09-06 04:01:01 |
Message-ID: | 4BEE2841-4E25-401F-A0C6-6EF7F4070799@sitening.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sep 5, 2005, at 10:51 PM, Alvaro Herrera wrote:
> On Mon, Sep 05, 2005 at 10:35:49PM -0500, Thomas F. O'Connell wrote:
>
>> I don't think any such behavior exists in PostgreSQL, and based on a
>> reading of the behavior in MySQL, I can't imagine it ever existing
>> considering the preference of PostgreSQL developers for correct (and
>> sane) behavior. INSERT IGNORE seems like a foot-cannon...
>>
>
> What is it supposed to do? If ignoring errors is the behavior
> Cristian
> wants, it's possible to do with savepoints (or PL/pgSQL exceptions).
Yeah, I think savepoints might be his best bet. It sounded like he
was explicitly trying to avoid PL/pgSQL.
Cristian, here's a pointer to the SAVEPOINT docs:
http://www.postgresql.org/docs/8.0/static/sql-savepoint.html
I was mostly remarking that I couldn't envision a flipped switch for
incorrect/non-standard INSERT behavior.
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-469-5150
615-469-5151 (fax)
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Cook | 2005-09-06 10:13:57 | Installation problem |
Previous Message | Alvaro Herrera | 2005-09-06 03:51:42 | Re: Insert Ignore or something similar... |