| From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | Lori Corbani <Lori(dot)Corbani(at)jax(dot)org>, Lori Corbani <lec(at)informatics(dot)jax(dot)org>, Richard Huxton <dev(at)archonet(dot)com> |
| Subject: | Re: function within a function/rollbacks/exception handling |
| Date: | 2011-11-08 15:21:34 |
| Message-ID: | 201111080721.35193.adrian.klaver@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tuesday, November 08, 2011 7:13:03 am Lori Corbani wrote:
> Richard,
>
> I manage to find one comment about an implicit rollback in a section of
> the developer's guide when porting from Oracle-to-Postgres: "when an
> exception is caught by an EXECPTION clause, all database changes since
> the block's BEGIN are automatically rolled back"
>
> Do you know of any other place in the documentation this discusses the
> implicit rollback in more detail? Or do you know of a good online site
> that contains some good examples or best-practices for these
> function-to-function calls?
http://www.postgresql.org/docs/9.0/interactive/plpgsql-control-
structures.html#PLPGSQL-ERROR-TRAPPING
>
> We are starting to port our Sybase database (200 stored procedures) over
> to Postgres and I am finding the online Postgres documentation and the
> Douglas book a bit lacking in some of the more specific examples that I
> am interested in finding.
>
> Thanks.
> Lori
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vick Khera | 2011-11-08 16:28:29 | Re: Masquerading a unique index as a primary key in 8.4? |
| Previous Message | Lori Corbani | 2011-11-08 15:13:03 | Re: function within a function/rollbacks/exception handling |