| From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | "Pit M(dot)" <fmi-soft(at)gmx(dot)de> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: transaction problem using cursors |
| Date: | 2007-06-11 13:36:06 |
| Message-ID: | 162867790706110636t5f1324a8gf7f1a0de23ecdb21@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> Unfortunately this is not possible, because this should happen on the
> client. The client calls FETCH for every record available in that cursor
> when the user (application) wants to display the data (scrollable
> list of records)
> So do you think i should wrap each FETCH statement?
> We handle exceptions errors through libpq, and if a FETCH leads to such
> a runtime error, we try to FETCH the first record again.
> The problem is that we can't use this cursor any more -> it seems to be
> corrupt after that error.
>
Change your SQL statement. It is not correct with your real data.
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pit M. | 2007-06-11 13:38:58 | Re: transaction problem using cursors |
| Previous Message | Michael Fuhr | 2007-06-11 13:34:25 | Re: Functions that return both Output Parameters and recordsets |