We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Statement::bind*() methods return a boolean value to indicate whether the binding was successful:
Statement::bind*()
dbal/lib/Doctrine/DBAL/Driver/Statement.php
Lines 51 to 53 in df43437
This value is ignored in other DBAL components. For instance:
dbal/lib/Doctrine/DBAL/Driver/OCI8/OCI8Statement.php
Lines 391 to 394 in 2ec1743
It leads to the issues like:
use Doctrine\DBAL\DriverManager; $conn = DriverManager::getConnection([ 'driver' => 'oci8', 'host' => 'localhost', 'user' => 'system', 'password' => 'oracle', 'dbname' => 'XE', ]); $data = $conn->fetchAll('SELECT 1 FROM DUAL', [123]); var_dump($data); /* Warning: oci_bind_by_name(): ORA-01036: illegal variable name/number in lib/Doctrine/DBAL/Driver/OCI8/OCI8Statement.php on line 316 array(1) { [0] => array(1) { [1] => string(1) "1" } } */
Statement::execute() should throw an exception in the case of a binding error instead of trying to execute an incorrectly constructed query.
Statement::execute()
The text was updated successfully, but these errors were encountered:
Handled in #3369
Sorry, something went wrong.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
morozov
No branches or pull requests
Statement::bind*()
methods return a boolean value to indicate whether the binding was successful:dbal/lib/Doctrine/DBAL/Driver/Statement.php
Lines 51 to 53 in df43437
This value is ignored in other DBAL components. For instance:
dbal/lib/Doctrine/DBAL/Driver/OCI8/OCI8Statement.php
Lines 391 to 394 in 2ec1743
It leads to the issues like:
Statement::execute()
should throw an exception in the case of a binding error instead of trying to execute an incorrectly constructed query.The text was updated successfully, but these errors were encountered: