If you want to use prepare like that then you’ll need to make a couple changes: The PostgreSQL driver wants to see numbered placeholders ($1, $2, …) not question marks and you need to give your prepared statement a name: ActiveRecord::Base.connection.raw_connection.prepare(‘some_name’, “DELETE FROM my_table WHERE id = $1”) The calling sequence is prepare followed by … Read more
You need to use: preparedStatement.executeQuery(); instead of preparedStatement.executeQuery(login); when you pass in a string to executeQuery() that query is executed literally and thus the ? is send to the database which then creates the error. By passing query string you are not execution the “cached” prepared statement for which you passed the values.
Because parameters specified in returning clauses are handled in a different way compared to normal output parameters(getReturnResultSet vs getResultSet vs returning parameters in a callablestatement). They need to be handled with OraclePreparedStatement. In the second case when you wrap the insert statement in begin..end the insert is handled by the database itself and al jdbc … Read more
I’m copying the solution into this answer so this can be given an upvote, otherwise the question will appear in the “unanswered questions” forever. I’m marking this answer CW so I won’t get any points. @Andrew E. says: I just turned on mysqli_report(MYSQLI_REPORT_ALL) to get a better understanding of what was going on – turns … Read more
This behaviour is quite annoying since JSON strings are accepted without problems when used as literal strings in SQL commands. There is a already an issue for this in the postgres driver Github repository (even if the problem seems the be the serverside processing). Besides using a cast (see answer of @a_horse_with_no_name) in the sql … Read more
You have to pass parameters to bind_param() by reference, which means you have to pass a single variable (not a concatenated string). There’s no reason you can’t construct such a variable specifically to pass in, though: $className=”%” . $this->className . ‘%’; $query->bind_param(‘s’, $className);
According to the node-sqlite3 API documentation, you can use parameters in your SQL queries in several different ways: // Directly in the function arguments. db.run(“UPDATE tbl SET name = ? WHERE id = ?”, “bar”, 2); // As an array. db.run(“UPDATE tbl SET name = ? WHERE id = ?”, [ “bar”, 2 ]); // … Read more
The notion that prepared statements are primarily about performance is something of a misconception, although it’s quite a common one. Another poster mentioned that he noted a speed improvement of about 20% in Oracle and SQL Server. I’ve noted a similar figure with MySQL. It turns out that parsing the query just isn’t such a … Read more
You can do like this: $sql = SELECT * FROM tbl_news ORDER BY date DESC LIMIT :start, :rows”; $q = $db->prepare($sql); $q->bindParam(‘:start’, $start, PDO::PARAM_INT); $q->bindParam(‘:rows’,$rows, PDO::PARAM_INT);
You can instantiate your connection to the database in a class that implement the singleton pattern. The connection will be done once and this class will be easily accessible by all of your other objects / scripts. i use a class called “Core” in the following example; class Core { public $dbh; // handle of … Read more