The use in MssqlBlob could never be reached, since the test used `&&`
rather than `||`.
The use in DatabaseMssql should never be reached, and all our other
Database subclasses will give PHP warnings or errors when it tries to
stringify an array or object rather than silently serializing. MSSQL
should be consistent there. Further, MSSQL never *un*serializes, so it
seems rather useless anyway.
Change-Id: I7b193c6be28662edb38d416ac02371f7a293ab56
}
if ( is_null( $value ) ) {
$sql .= 'null';
- } elseif ( is_array( $value ) || is_object( $value ) ) {
- if ( is_object( $value ) && $value instanceof Blob ) {
- $sql .= $this->addQuotes( $value );
- } else {
- $sql .= $this->addQuotes( serialize( $value ) );
- }
} else {
$sql .= $this->addQuotes( $value );
}
/** @noinspection PhpMissingParentConstructorInspection */
/**
- * @param Blob|array|string $data
+ * @param Blob|string $data
*/
public function __construct( $data ) {
if ( $data instanceof MssqlBlob ) {
$this->data = $data->data;
} elseif ( $data instanceof Blob ) {
$this->data = $data->fetch();
- } elseif ( is_array( $data ) && is_object( $data ) ) {
- $this->data = serialize( $data );
} else {
$this->data = $data;
}