Recently we've been having problems with MySQL at work. Looks like Alan Burlison is experiencing the same kind of thing. If you're at OSCON, can you bop the free database developers on the head? How can they load everything into memory by default? No cursors? They all suck! All! Suck! Software! Graahahahgggh.
Hmmmm, maybe this post should have been on hates-software...
Re:Lose MySQL... use PostgreSQL instead
vek on 2004-07-28T04:41:16
PostgreSQL is real. Cursors, etc.
But I thought Leon's point 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 into data structures located in the frontend application. This has to be considered when selecting large amounts of data!
