From: | Keary Suska <hierophant(at)pcisys(dot)net> |
---|---|
To: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: is there any replacement for a cursor |
Date: | 2001-09-27 19:24:12 |
Message-ID: | B7D8D8FB.3C34%hierophant@pcisys.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Not as easy a one. The next best alternative would be using a temporary
table and LIMIT clauses, but I am not sure how that compares performance
wide as well as why you want to avoid cursors in the first place. There has
been a discussion regarding maintaining a persistent selection for web
application use, where cursors aren't always the best soution.
Keary Suska
Esoteritech, Inc.
"Leveraging Open Source for a better Internet"
> From: srinivas <srinivaschowdary(at)essemm(dot)co(dot)in>
> Date: Tue, 25 Sep 2001 11:25:25 +0530
> To: "'pgsql-general(at)PostgreSQL(dot)org'" <pgsql-general(at)postgresql(dot)org>
> Subject: [GENERAL] is there any replacement for a cursor
>
> can iknow is there any replacement for a cursor in postgresql if soon
> please send me the information as soon as u can.waiting for ur reply.
> cheers
> chowdary.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mitch Vincent | 2001-09-27 19:26:50 | Re: backend stalls |
Previous Message | Keary Suska | 2001-09-27 19:18:53 | Re: How to store empty to Date field ? |