Hi, (from an regular reader but first time writer to this list) Jay Pipes wrote: >> As far as selects go, I certainly have used them there. A common from >> page query for slashdot for example had just two parameters and was >> called constantly for the page. In that instance a prep stmt was a big >> win (same for the SELECT *FROM USER WHERE user_id=?). > > ? This doesn't make sense to me. In what way does "SELECT * FROM USER > WHERE user_id = ?" benefit from preparation if the connector does not > keep the statement around? In other words, if the connection is closed > upon end of the web request, what point does this have?
There is more than PHP out there ;-) In Java EE Application Server you usually use a connection pool, mostly because for other databases (e.g. Oracle) the overhead for creating a new connection is quite high. At the end of a request the connection is passed back to the pool and the next request reuses the same connection (or another from the pool). In such a scenario prepared statements, even if they are bound to a connection, do make sense or do I miss something? regards, Raphael _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
