PdoSessionHandler::write()

write($sessionId, $data) {@inheritdoc} Parameters $sessionId $data

PdoSessionHandler::read()

read($sessionId) {@inheritdoc} Parameters $sessionId

PdoSessionHandler::open()

open($savePath, $sessionName) {@inheritdoc} Parameters $savePath $sessionName

PdoSessionHandler::isSessionExpired()

bool isSessionExpired() Returns true when the current session exists but expired according to session.gc_maxlifetime. Can be used to distinguish between a new session and one that expired due to inactivity. Return Value bool Whether current session expired

PdoSessionHandler::gc()

gc($maxlifetime) {@inheritdoc} Parameters $maxlifetime

PdoSessionHandler::destroy()

destroy($sessionId) {@inheritdoc} Parameters $sessionId

PdoSessionHandler::createTable()

createTable() Creates the table to store sessions which can be called once for setup. Session ID is saved in a column of maximum length 128 because that is enough even for a 512 bit configured session.hash_function like Whirlpool. Session data is saved in a BLOB. One could also use a shorter inlined varbinary column if one was sure the data fits into it. Exceptions PDOException When the table already exists DomainException When an unsupported PDO driver is used

PdoSessionHandler::close()

close() {@inheritdoc}

PdoSessionHandler

class PdoSessionHandler implements SessionHandlerInterface Session handler using a PDO connection to read and write data. It works with MySQL, PostgreSQL, Oracle, SQL Server and SQLite and implements different locking strategies to handle concurrent access to the same session. Locking is necessary to prevent loss of data due to race conditions and to keep the session data consistent between read() and write(). With locking, requests for the same session will wait until the other one finished

PdoProfilerStorage deprecated::write()

bool write(Profile $profile) Saves a Profile. Parameters Profile $profile A Profile instance Return Value bool Write operation successful