Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If I may understand you correctly, what you're trying to do is to have some sort of per-session error log, which can be read later on. </p> <p>My suggestion is to create separate log file per session, you can identify the log file by using the session id, which is unique per session.</p> <pre><code>&lt;?php define('PER_SESSION_LOG_PATH', '/tmp/logs/'); //or whatever path /* return log handle */ class SessionLogger { static $fh; static function log_path() { return PER_SESSION_LOG_PATH . session_id() . '.log'; } static function log_open() { if (!self::$fh) { self::$fh = fopen(self::log_path(), 'a+'); } return self::$fh; } static function add_log($errors) { if (self::log_open()) { fwrite(self::$fh, serialize($errors) . PHP_EOL); } } static function log_close() { if (self::$fh) { fclose(self::$fh); } } //note that if the size of the log file is larger than memory_limit, you //may run into problems. //returns all the logs static function get_logs($truncate = TRUE) { $logs = array(); if (self::log_open()) { while (!feof(self::$fh)) { $logs[] = unserialize(fgets(self::$fh)); } //if the logs should be clear, then... if ($truncate) { fclose(self::$fh); //close and nullify handle self::$fh = null; unlink(self::log_path()); //then delete log file. } } return $logs; } } </code></pre> <p>Then you can add errors by doing</p> <pre><code>SessionLogger::add_log($error); </code></pre> <p>You can also read the logs by doing</p> <pre><code>SessionLogger::get_logs(true); //or false if you don't want to delete file. </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POMax depth of Session-array
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UStlogbon
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMax depth of Session-array
      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. VTAcceptedByOriginator
    1. COThanks, that's a good solution. But isn't this much slower than storing it in the session? (I have many file-operations, and the session might be in the RAM all the time)
      singulars
      1. PO
      1. USmaja
    2. COExcept you're using a RAM store or database store, your session will still be written to file after every request, you can modify this code to only write to the file on shutdown. Unlike when you're using session, in which all the data in file are loaded to RAM on request start up, this will only do an incremental write of errors generated in a single request, thus conserving RAM.
      singulars
      1. PO
      1. UStlogbon
 

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