Important

New database features are no longer connected to engine versions; features are now enabled independently during scheduled update windows, and “major” and “minor” releases no longer exist in Helios. Please visit the release notes to view the latest features available in your database clusters.

Using Prepared Statements

Note

For SingleStore Helios, use the endpoint (available in the Cloud Portal) to run the commands discussed in this topic.

If you are using an older version of SingleStore Helios, or using SingleStore Helios with Audit Logging enabled, SingleStore does not support server-side prepared statements. Instead, many client drivers support a configuration option to allow client-side prepared statements. This configuration option may also be referred to as client-side prepared statement emulation or parameter interpolation. You can use the same code in your application, but change a flag in the client driver configuration. For example:

In the MySQL Connector/J (JDBC) driver, set useServerPrepStmts=false, which is the default configuration.
In MariaDB Connector/J, set useServerPrepStmts=false.
In ODBC, set no_ssps=1.
In the Go MySQL driver, set interpolateParams=true.
In PHP PDO, set PDO::ATTR_EMULATE_PREPARES=TRUE.

In many other databases, server-side prepared statements provide performance advantages, but SingleStore Helios already compiles and caches query plans internally, so SingleStore Helios does not need server-side prepared statements to get most of those performance advantages.

Using Prepared Statements

Was this article helpful?

Was this article helpful?