Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Honestly, I think you're trying to solve the wrong problem. If you're sleeping the class, then isn't it wrong to have a successful sleep if you can't serialize everything? Otherwise you can wake up to an inconsistent state (or at least a state that's different than the current one). So I would argue that you should just put everything into the resultant array and then let PHP tell you if it's not serializable.</p> <p>Otherwise, do you then need to check to see if any stored objects are serialzable? Should you then be checking for <code>Serializable</code> interface or the existence of <code>__sleep</code>? Where do you draw the line? So I would say that you should only not serialize resources and variables that you explicitly know how to recreate in the wakeup function (such as a database connection, or any closures you explicitly know how to recreate). But be careful here, since if you let those closures/resources be changed via the object's API, how can you be sure of a successful wakeup to the prior state.</p> <p>So in short, I would recommend just returning everything, and letting PHP handle unserializable variables. Otherwise you'd need to either white-list (which isn't going to be practical) or black-list (which isn't going to be complete). And neither is a great solution. Just handle the exception when it comes (throwing and catching exceptions isn't bad).</p> <p>As far as your exact question, I would implement it as follows:</p> <pre><code>function is_closure($callback) { $func = function(){}; return $callback instanceof $func; } </code></pre> <p>It still relies on the implementation detail of the closure being of a Object type, but I think that's the best we can do at this point. The best solution would be to petition the core to add a <code>is_closure()</code> function which would be implementation independent...</p>
    singulars
    1. This table or related slice is empty.
    1. POdetect closure in __sleep to prevent their serialization
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USircmaxell
    1. USircmaxell
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POdetect closure in __sleep to prevent their serialization
      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. VTAcceptedByOriginator
    1. COThanks. I also felt solving the wrong problem. I came up with a solution which at least pushes the knowledge to serialize or not to the closure itself, which avoids the black/whitelisting.
      singulars
      1. PO
      1. USrgroli
 

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