function IPDOStatement.closeCursor: Boolean;

IPDOStatement.closeCursor frees up the connection to the server so that other SQL statements may be issued, but leaves the statement in a state that enables it to be executed again.

This method is useful for database drivers that do not support executing a IPDOStatement 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.

IPDOStatement.closeCursor is implemented either as an optional driver specific method (allowing for maximum efficiency), or as the generic PDO fallback if no driver specific function is installed. The PDO generic fallback is semantically the same as writing the following code in your pascal code:

   while (stmt.fetch(row)) do
      if not stmt.nextRowSet then break;

Example

In the following example, the stmt IPDOStatement object returns multiple rows but the application fetches only the first row, leaving the PDOStatement object in a state of having unfetched rows. To ensure that the application will work with all database drivers, the author inserts a call to IPDOStatement.closeCursor on stmt before executing the otherStmt IPDOStatement object.

{ Create a PDOStatement object }
  stmt := db.prepare_as_is ('SELECT foo FROM bar');

{ Create a second PDOStatement object }
  otherStmt = db.prepare_as_is('SELECT foobaz FROM foobar');

{ Execute the first statement }
  stmt.execute;

{ Fetch only the first row from the results }
  stmt.fetch (row);

{ The following call to closeCursor() may be required by some drivers }
  stmt.closeCursor;

{ Now we can execute the second statement }
  otherStmt.execute();