That's the impression that I get as well - one query at a time. So, you can start a slow query and do other stuff while waiting, just not other database stuff. Or you can have multiple handles. Perhaps one handle for quick stuff and another async handle for the slow queries.
Alas no, still missing [cpan.org]. Which is a shame really. You've just got to be careful when iterating over large datasets. Those coming from MySQL or Oracle can get bitten by this. Ahem. No, this never happened to me;-)
Therefore the execute method fetches all data at once into data structures located in the front-end application. This fact must to be considered when selecting large amounts of data!
Async++ (Score:1)
Yeah this looks cool. Asychronous query capability, that's hot.
Re: (Score:1)
Isn't this the first implementation of this feature for a DBI module?
Re: (Score:1)
Looks pretty straight forward to me [cpan.org] :)
Ordinary morality is for ordinary people. -- Aleister Crowley
Re: (Score:1)
pg_ready can be called on a statement handle. But pg_result can not. So no help there.
Can you only have one async query at any given time? Guess I have to try it out.
Re: (Score:1)
Ooooh, Cursor Support Perhaps? (Score:2)
Therefore the execute method fetches all data at once into data structures located in the front-end application. This fact must to be considered when selecting large amounts of data!