Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • But I would say, relational databases. As one of my recent posts on my journal says, DB_File and MLDBM rockz :)
  • PostgreSQL is real. Cursors, etc. Why anyone still chooses MySQL for a reason other than legacy (people compatibility, software compatibility) in this day and age still confuses me.
    --
    • Randal L. Schwartz
    • Stonehenge
    • PostgreSQL is real. Cursors, etc.

      But I thought Leon's point [postgresql.org] was that DBD::Pg's support of cursors is the problem here.

      From the DBD::Pg docs (emphasis mine):

      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 i