Doc #78597 [Opn->Nab]: MySQL Feature Comparison update

From: Date: Wed, 25 Sep 2019 22:30:13 +0000
Subject: Doc #78597 [Opn->Nab]: MySQL Feature Comparison update
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to doc-bugs+get-16966@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=78597&edit=1 ID: 78597 Updated by: requinix@php.net Reported by: Mike+PHP at HiMikeB dot com Summary: MySQL Feature Comparison update -Status: Open +Status: Not a bug Type: Documentation Problem Package: MySQLi related Operating System: All PHP Version: Irrelevant Block user comment: N Private report: N New Comment: > The table indicates mysqli does not support prepared statements. *Client-side* statements. Client-side statements are what PDO's emulated prepares are: an API that makes it look to the developer like they're working with prepared statements, with placeholders and bindings and all that, except what actually happens internally is that it builds the query as a string and sends it to the server as a normal (un-prepared) query. And mysqli doesn't do that. It doesn't have a way to toggle between whether the statement is prepared on the server or "prepared" on the client. It only does the regular server-side prepared statements. Which is totally okay. Previous Comments: ------------------------------------------------------------------------ [2019-09-25 21:27:30] Mike+PHP at HiMikeB dot com Description: ------------ --- From manual page: https://php.net/mysqlinfo.api.choosing --- The table indicates mysqli does not support prepared statements. Just trying to reconcile with this link, and is it still true or am I misunderstanding something? https://www.php.net/manual/en/mysqli-stmt.bind-param.php "Binds variables to a prepared statement as parameters" What type of client-side prepared statement does mysqli not support? ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=78597&edit=1

« previous php.doc.bugs (#16966) next »