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@essemm.co.in>
> Date: Tue, 25 Sep 2001 11:25:25 +0530
> To: "'pgsql-general@PostgreSQL.org'" <pgsql-general@postgresql.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@postgresql.org
>
