Databases

RFC #0159: Deadlock handling

Scope of Change
A new class rdbms.SQLDeadlockException will be introduced. The rdbms drivers will handle dead lock situations specially and throw this new exception instead of a generic SQLStatementFailedException.

Rationale
Deadlocks are a very special case in database systems and often need special programmatic handling.

Read the full RFC here

Tracking SQL statements sent

The XP framework's RDBMS access API offers logging of SQL queries sent to the server by adding observers to database connections:

<?php 
  // First, set up logger
  Logger::getInstance()->getCategory('sql')->addAppender(new ConsoleAppender());
 
  // Retrieve connection and add the log observer for the "sql" category to the connection
  $conn= DriverManager::getConnection('sybase://user:pass@dbserv01');
  $conn->addObserver(LogObserver::instanceFor('sql'));
?>

Database logging beautified

On a short note: Database logging output has been made more condense.

Old output:

[23:05:34 4248 debug] rdbms.DBEvent(query) {'select max(account_id) as `value` from test.account'} 
[23:05:34 4248 debug] rdbms.DBEvent(queryend) {MySQLResultSet::__set_state(array(
   'handle' => NULL,
   'fields' => 
  array (
    'value' => 'int',
  ),
   '__id' => NULL,
))}

[23:06:09 4232 debug] rdbms.DBEvent(query) {"select max(account_id) as `value` from test.account"} 
[23:06:09 4232 debug] rdbms.DBEvent(queryend) {rdbms.mysql.MySQLResultSet(Resource id #140)@[
  value => "int"
]}

RFC #0131: Query class and operation

Scope of Change
Extends the rdbms critertia api

• Query class that stores complete querys
• set operations like union, intercept and except

• Store complete queries.
• Provide a tool to represent set operations in criteria / OO world.

Subscribe

You can subscribe to the XP framework's news by using RSS syndication.

Categories