It's always good to close your cursors once you don't need them anymore,
but PostgreSQL doesn't force you to or blocks if you don't.
I really wonder why people use senseless things like PDO. Ah yes.. it's
all about design patterns, right. Let's write a wrapper for the sole
purpose of having written a wrapper. Sounds like a great pattern.
Yonatan Ben-Nes wrote:
I know that it's also related to PHP but sadly no one knew anything
there so
I try here... :)
At the PHP manual of
PDOStatement::closeCursor<http://il.php.net/manual/en/function.pdostatement-closecursor.php>it's
written that "This method is useful for database drivers that do not
support executing a PDOStatement object when a previously executed
PDOStatement object still has unfetched rows. If your database driver
suffers from this limitation, the problem may manifest itself in an
out-of-sequence error.".
Anyone know if the PostgreSQL driver suffer from this problem or not?
--
Best regards,
Hannes Dorbath
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
