Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Alias (5735)

  (email not shown publicly)

Journal of Alias (5735)

Wednesday January 16, 2008
07:58 AM

DBD::Pg 2.0.0 coming soon!

[ #35401 ]

I normally don't like to link to other people's blogs, but this is one announcement I think people may have missed, that is extremely exciting.

It looks like the driver to everybody's favourite ACID-compliant database is getting a major new release!

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Yeah this looks cool. Asychronous query capability, that's hot.

    • I haven't had time to look at the docs. I wonder how async q's are going to work.

      Isn't this the first implementation of this feature for a DBI module?
      • --
        Ordinary morality is for ordinary people. -- Aleister Crowley
        • I wonder why it's a DB handle method. How do you keep track of several async queries?

          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.
          • 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 []. 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!