| From: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
|---|---|
| To: | "Craig Ringer" <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | "Flavio Palumbo" <f(dot)palumbo(at)silmasoftware(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: strange commit behavior |
| Date: | 2008-11-18 13:37:10 |
| Message-ID: | 2f4958ff0811180537r53c3b9bdga5fa581a8a10b8a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Nov 18, 2008 at 1:25 PM, Craig Ringer
<craig(at)postnewspapers(dot)com(dot)au>wrote:
>
>
> You can use savepoints (see the manual) to recover from errors, though
> they have some issues if you use hundreds of thousands of savepoints in
> a single transaction. It's much better to check the data on INSERT to
> make sure it's OK. You can do this with an INSERT ... SELECT (and check
> the rowcount), with a PL/PgSQL function that returns a result value, do
> it client-side, etc.
>
can you post an example ?
would that also resolve problem with 'rowcount' left unset, if trigger or
rule is used on table ?
--
GJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gustavo Rosso | 2008-11-18 14:25:16 | Urgent - Grant |
| Previous Message | A. Kretschmer | 2008-11-18 13:33:12 | Re: Urgent - Grant |