From: | Joshua Jore <moomonk(at)daisy-chan(dot)org> |
---|---|
To: | Mithun Bhattacharya <mithun(dot)b(at)egurucool(dot)com> |
Cc: | PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Newbie DBD::Pg question |
Date: | 2001-07-06 17:32:06 |
Message-ID: | Pine.BSO.4.33.0107061231280.20677-100000@aaieee.daisy-chan.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I haven't gotten into it yet but you could try using the sendQuery method
and looping on the new data as it becomes available.
Josh
On Fri, 6 Jul 2001, Mithun Bhattacharya wrote:
> Just started on postgres a few days back and was having a few questions
> about the perl interface to it. According to perldoc DBD::Pg
> ----------------
> Cursors
>
> Although PostgreSQL has a cursor concept, it has not been
> used in the current implementation. Cursors in PostgreSQL
> can only be used inside a transaction block. Because only
> one transaction block at a time is allowed, this would
> have implied the restriction, not to use any nested SELECT
> statements. Hence the execute method fetches all data at
> once into data structures located in the frontend
> application. This has to be considered when selecting
> large amounts of data !
> -----------------
> Frankly speaking I am not sure what the Author is saying here. Anybody
> cares to point me in the right direction ??? I do have to extract large
> amount of data but I am not sure whether it affects me or not.
>
>
> Mithun
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2001-07-06 17:32:09 | Re: query syntax change? |
Previous Message | Jared H. Hudson | 2001-07-06 17:25:21 | SELECT'ing a function call |