Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Nope.<br> That's interesting question and I spent some good time investigating it.<br> There is no way to pass a prepared statement between calls. </p> <p>And, honestly, speed gain is not that great to talk about. </p> <p>If you're concerned in performance - turn to the <strong>queries</strong>, not to mere a driver.<br> It's queries that affect performance, not the way they re called.</p> <p>errr..<br> after reading your question more throughly, I didn't change my mind, but there are some things to note</p> <blockquote> <p>high volume of tiny REST requests which will mostly be doing small queries and returning them to the browser to deal with will end up doing a lot of redundant work for each request.</p> </blockquote> <p>That's right.<br> So, consider to reduce that number by sending requests in batches and requesting more info in one. Not because of negligible difference in prepared statements but because of <strong>considerable network latency</strong>.</p> <blockquote> <p>I would expect to reduce the apache server to mysql server overhead substantially.</p> </blockquote> <p>And this one is not.<br> Looks like you're taking prepared statements wrong and confusing them with query cache.<br> Even if you manage to get prepared statements to persist between requests, it won't affect whatever apache to mysql interchange - you need to <em>execute</em> every subsequent call to prepared statement, means send request to mysql server. So, the only thing you save on is just query parsing which is blazingly fast nowadays. I mean unnoticeable fast. </p>
    singulars
    1. This table or related slice is empty.
    1. POIs it possible to store a PDO prepared statement in PHP / Mysql / APC / Memcache for reuse?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USYour Common Sense
    1. USYour Common Sense
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs it possible to store a PDO prepared statement in PHP / Mysql / APC / Memcache for reuse?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf you read the link I supplied it does mention prepared statments using the query cache: "Before MySQL 5.1.17, prepared statements do not use the query cache. Beginning with 5.1.17, prepared statements use the query cache under certain conditions, which differ depending on the preparation method:" This leaves me unclear as to if a new PDO prepare with the same query but different values will hit the cache, even if it is still there. Can you explain / back up your statement that there is no way? Did you actually try and stick the handle in memory cache (I might do this for the learning)
      singulars
      1. PO
      1. USJared Chmielecki
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload