escaped the periods as per review comments
This commit is contained in:
parent
0d4e6373a0
commit
0b6565da67
|
@ -60,10 +60,10 @@ Test new connection keyword ColumnEncryption
|
|||
echo "Done\n";
|
||||
?>
|
||||
--EXPECTREGEX--
|
||||
Connected successfully with ColumnEncryption enabled.
|
||||
Failed to connect.
|
||||
Connected successfully with ColumnEncryption enabled\.
|
||||
Failed to connect\.
|
||||
SQLSTATE\[08001\]: .*\[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]Invalid value specified for connection string attribute 'ColumnEncryption'
|
||||
Failed to connect.
|
||||
Failed to connect\.
|
||||
SQLSTATE\[08001\]: .*\[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]Invalid value specified for connection string attribute 'ColumnEncryption'
|
||||
Connected successfully with ColumnEncryption disabled.
|
||||
Connected successfully with ColumnEncryption disabled\.
|
||||
Done
|
|
@ -72,29 +72,29 @@ Connect using a custom keystore provider with some required inputs missing
|
|||
echo "Done\n";
|
||||
?>
|
||||
--EXPECTREGEX--
|
||||
Connecting... with column encryption
|
||||
Connected successfully with ColumnEncryption enabled and KSP specified.
|
||||
Connecting\.\.\. with column encryption
|
||||
Connected successfully with ColumnEncryption enabled and KSP specified\.
|
||||
|
||||
Connecting... with an invalid input to CEKeystoreProvider
|
||||
Connecting\.\.\. with an invalid input to CEKeystoreProvider
|
||||
Failed to connect.
|
||||
SQLSTATE\[HY024\]: \[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]Invalid attribute value
|
||||
|
||||
Connecting... with an empty path
|
||||
Connecting\.\.\. with an empty path
|
||||
Failed to connect.
|
||||
SQLSTATE\[IMSSP\]: Invalid value for loading a custom keystore provider.
|
||||
SQLSTATE\[IMSSP\]: Invalid value for loading a custom keystore provider\.
|
||||
|
||||
Connecting... without a path
|
||||
Connecting\.\.\. without a path
|
||||
Failed to connect.
|
||||
SQLSTATE\[IMSSP\]: The path to the custom keystore provider is missing.
|
||||
SQLSTATE\[IMSSP\]: The path to the custom keystore provider is missing\.
|
||||
|
||||
Connecting... without a name
|
||||
Connecting\.\.\. without a name
|
||||
Failed to connect.
|
||||
SQLSTATE\[IMSSP\]: The name of the custom keystore provider is missing.
|
||||
SQLSTATE\[IMSSP\]: The name of the custom keystore provider is missing\.
|
||||
|
||||
Connecting... without a key
|
||||
Connecting\.\.\. without a key
|
||||
Failed to connect.
|
||||
SQLSTATE\[IMSSP\]: The encryption key for the custom keystore provider is missing.
|
||||
SQLSTATE\[IMSSP\]: The encryption key for the custom keystore provider is missing\.
|
||||
|
||||
Connecting... with all required inputs
|
||||
Connected successfully with ColumnEncryption enabled and KSP specified.
|
||||
Connecting\.\.\. with all required inputs
|
||||
Connected successfully with ColumnEncryption enabled and KSP specified\.
|
||||
Done
|
|
@ -68,7 +68,7 @@ RunTest();
|
|||
?>
|
||||
--EXPECTREGEX--
|
||||
|
||||
Starting test...
|
||||
Starting test\.\.\.
|
||||
Setting query timeout as an attribute in connection
|
||||
array\(3\) \{
|
||||
\[0\]=>
|
||||
|
|
|
@ -90,12 +90,12 @@ Repro();
|
|||
?>
|
||||
--EXPECTREGEX--
|
||||
|
||||
Test begins...
|
||||
\[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]\[SQL Server\]Cannot insert explicit value for identity column in table '.+' when IDENTITY_INSERT is set to OFF.
|
||||
Test begins\.\.\.
|
||||
\[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]\[SQL Server\]Cannot insert explicit value for identity column in table '.+' when IDENTITY_INSERT is set to OFF\.
|
||||
544
|
||||
23000
|
||||
Number of rows inserted: 2
|
||||
Number of rows fetched: 2
|
||||
|
||||
Done
|
||||
Test "sqlsrv_statement_complex_query" completed successfully.
|
||||
Test \"sqlsrv_statement_complex_query\" completed successfully\.
|
||||
|
|
|
@ -39,7 +39,7 @@ Array
|
|||
\[SQLSTATE\] => 22018
|
||||
\[1\] => 245
|
||||
\[code\] => 245
|
||||
\[2\] => \[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]\[SQL Server\]Conversion failed when converting the varchar value 'null' to data type int.
|
||||
\[message\] => \[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]\[SQL Server\]Conversion failed when converting the varchar value 'null' to data type int.
|
||||
\[2\] => \[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]\[SQL Server\]Conversion failed when converting the varchar value 'null' to data type int\.
|
||||
\[message\] => \[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]\[SQL Server\]Conversion failed when converting the varchar value 'null' to data type int\.
|
||||
\)
|
||||
Done
|
|
@ -39,7 +39,7 @@ Array
|
|||
\[SQLSTATE\] => 22018
|
||||
\[1\] => 245
|
||||
\[code\] => 245
|
||||
\[2\] => \[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]\[SQL Server\]Conversion failed when converting the nvarchar value '银河' to data type int.
|
||||
\[message\] => \[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]\[SQL Server\]Conversion failed when converting the nvarchar value '银河' to data type int.
|
||||
\[2\] => \[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]\[SQL Server\]Conversion failed when converting the nvarchar value '银河' to data type int\.
|
||||
\[message\] => \[Microsoft\]\[ODBC Driver 1[1-9] for SQL Server\]\[SQL Server\]Conversion failed when converting the nvarchar value '银河' to data type int\.
|
||||
\)
|
||||
Done
|
||||
|
|
|
@ -41,8 +41,8 @@ Array
|
|||
\[SQLSTATE\] => IMSSP
|
||||
\[1\] => -44
|
||||
\[code\] => -44
|
||||
\[2\] => The connection cannot process this operation because there is a statement with pending results. To make the connection available for other queries, either fetch all results or cancel or free the statement. For more information, see the product documentation about the MultipleActiveResultSets connection option.
|
||||
\[message\] => The connection cannot process this operation because there is a statement with pending results. To make the connection available for other queries, either fetch all results or cancel or free the statement. For more information, see the product documentation about the MultipleActiveResultSets connection option.
|
||||
\[2\] => The connection cannot process this operation because there is a statement with pending results\. To make the connection available for other queries, either fetch all results or cancel or free the statement\. For more information, see the product documentation about the MultipleActiveResultSets connection option\.
|
||||
\[message\] => The connection cannot process this operation because there is a statement with pending results\. To make the connection available for other queries, either fetch all results or cancel or free the statement\. For more information, see the product documentation about the MultipleActiveResultSets connection option\.
|
||||
\)
|
||||
|
||||
\[1\] => Array
|
||||
|
|
Loading…
Reference in a new issue