class MssqlDebugPDO extends MssqlPropelPDO
dblib doesn't support transactions so we need to add a workaround for transactions, last insert ID, and quoting
Constants
PROPEL_ATTR_CACHE_PREPARES |
Attribute to use to set whether to cache prepared statements. |
PROPEL_ATTR_CONNECTION_NAME |
Attribute to use to set the connection name usefull for explains |
DEFAULT_SLOW_THRESHOLD |
|
DEFAULT_ONLYSLOW_ENABLED |
|
Properties
$useDebug |
Methods
integer |
beginTransaction()
Begin a transaction. |
from MssqlPropelPDO |
integer |
commit()
Commit a transaction. |
from MssqlPropelPDO |
integer |
rollBack()
Roll-back a transaction. |
from MssqlPropelPDO |
integer |
forceRollBack()
Rollback the whole transaction, even if this is a nested rollback and reset the nested transaction count to 0. |
from MssqlPropelPDO |
integer | lastInsertId(string $seqname = null) | from MssqlPropelPDO |
string | quoteIdentifier(string $text) | from MssqlPropelPDO |
boolean | useQuoteIdentifier() | from MssqlPropelPDO |
Details
in MssqlPropelPDO at line 26
public integer
beginTransaction()
Begin a transaction.
It is necessary to override the abstract PDO transaction functions here, as
the PDO driver for MSSQL does not support transactions.
in MssqlPropelPDO at line 52
public integer
commit()
Commit a transaction.
It is necessary to override the abstract PDO transaction functions here, as
the PDO driver for MSSQL does not support transactions.
in MssqlPropelPDO at line 82
public integer
rollBack()
Roll-back a transaction.
It is necessary to override the abstract PDO transaction functions here, as
the PDO driver for MSSQL does not support transactions.
in MssqlPropelPDO at line 110
public integer
forceRollBack()
Rollback the whole transaction, even if this is a nested rollback and reset the nested transaction count to 0.
It is necessary to override the abstract PDO transaction functions here, as
the PDO driver for MSSQL does not support transactions.