| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | juleni(at)livetrade(dot)cz |
| Cc: | "Frank D(dot) Engel, Jr(dot)" <fde101(at)fjrhome(dot)net>, Juleni <julo(at)opensubsystems(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Select after insert to the unique column |
| Date: | 2004-12-13 16:44:25 |
| Message-ID: | 20041213164425.GB546@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Dec 13, 2004 at 17:04:17 +0100,
juleni(at)livetrade(dot)cz wrote:
> Thank you for your answer. I think it's very interesting behaviour. Is
> it a feature or bug ?
Until version 8 (which is in release candidate status now), there was
no way to recover from an error within a transaction other than aborting
the transaction. With version 8 you will be able to use savepoints to
allow for recovery from errors within a transaction.
The best answer to your question above, is that it is a limitation and
not really a feature and definitely not a bug.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jimmie H. Apsey | 2004-12-13 16:46:30 | subscribe missing? |
| Previous Message | Bruno Wolff III | 2004-12-13 16:37:45 | Re: table with sort_key without gaps |