Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This seemed like an interesting idea. What I came up with is essentially a small JavaScript class that overrides the console's functions (but allows the default behavior - you can still see the information in Google Chrome's Inspector, for example).</p> <p>It is pretty simple to use. Save this as 'consolelogger.js':</p> <pre><code>/** * ConsoleLogger * * Tracks the history of the console. * @author Johnathon Koster * @version 1.0.0 */ var ConsoleLogger = function() { // Holds an instance of the current object. var _instance = this; this._logOverwrite = function(o) { var _log = o.log; // Overwrites the console.log function. o.log = function(e) { _instance.pushLog(e); // Calls the console.log function (normal browser behavior) _log.call(o, e); } // Overwrites the console.info function. o.info = function(e) { _instance.pushInfoLog(e); // Calls the console.info function (normal browser behavior) _log.call(o, e); } // Overwrites the console.warn function. o.warn = function(e) { _instance.pushWarnLog(e); // Calls the console.warn function (normal browser behavior) _log.call(o, e); } // Overwrites the console.error function. o.error = function(e) { _instance.pushErrorLog(e); // Calls the console.error function (normal browser behavior) _log.call(o, e); } }(console); // Holds the history of the console calls made by other scripts. this._logHistory = []; this._infoHistory = []; this._warnHistory = []; this._errorHistory = []; this._windowErrors = []; /** * This allows users to get the history of items not explicitly added. */ window.onerror = function(msg, url, line) { _instance._windowErrors.push('Message: ' + msg + ' URL: ' + url + ' Line: ' + line); } /** * Adds an item to the log history. * * @param {log} object to log */ this.pushLog = function(log) { this._logHistory.push(log); } /** * Adds an item to the information log history. * * @param {log} object to log */ this.pushInfoLog = function(log) { this._infoHistory.push(log); } /** * Adds an item to the warning log history. * * @param {log} object to log */ this.pushWarnLog = function(log) { this._warnHistory.push(log); } /** * Adds an item to the error log history. * * @param {log} object to log */ this.pushErrorLog = function(log) { this._errorHistory.push(log); } /** * Returns the log history. * @this {ConsoleLogger} * @return {array} the log history. */ this.getLog = function() { return this._logHistory; } /** * Returns the information log history. * @this {ConsoleLogger} * @return {array} the information log history. */ this.getInfoLog = function() { return this._infoHistory; } /** * Returns the warning log history. * @this {ConsoleLogger} * @return {array} the warning log history. */ this.getWarnLog = function() { return this._warnHistory; } /** * Returns the error log history. * @this {ConsoleLogger} * @return {array} the error log history. */ this.getErrorLog = function() { return this._errorHistory; } /** * Returns the window log history. * @this {ConsoleLogger} * @return {array} the window log history. */ this.getWindowLog = function() { return this._windowErrors; } /** * Returns all log histories. * @this {ConsoleLogger} * @return {array} the error log(s) history. */ this.getLogHistory = function() { var _return = []; _return = this._logHistory _return = _return.concat(this._infoHistory); _return = _return.concat(this._warnHistory); _return = _return.concat(this._errorHistory); _return = _return.concat(this._windowErrors); return _return; } } </code></pre> <p>And add it to your page like this:</p> <pre><code>&lt;script src="consolelogger.js"&gt;&lt;/script&gt; &lt;script&gt; // Create a new instance of ConsoleLogger var logger = new ConsoleLogger; &lt;/script&gt; </code></pre> <p>Now, you don't have to do anything special to trap 'console.log', 'console.warn', 'console.info', or 'console.error'. The ConsoleLogger will do it for you, and allow you to get the history of what's been added.</p> <p>To retrieve the history call these functions (all of them return a JavaScript array):</p> <pre><code>var logHistory = logger.getLog(); // Get the console.log history var infoHistory = logger.getInfoLog(); // Get the console.info history var warningHistory = logger.getWarnLog(); // Get the console.warn history var errorHistory = logger.getErrorLog(); // Get the console.error history var windowLog = logger.getWindowLog(); // Get the window error history var allLogs = logger.getLogHistory(); // Returns all log histories as one array. </code></pre> <p>I apologize for such a lengthy post, but it seems to do the trick! I also created a <a href="https://github.com/paradoxonellc/ConsoleLogger" rel="nofollow">GitHub repo</a>; if I do any more work on it, changes will be committed there.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to get browser diagnostics
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJohn
    1. USJohn
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to get browser diagnostics
      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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COwill this catch the errors the browser shows in the console? Not just whatever I would send to console.log myself, but errors generated because of coding errors?
      singulars
      1. PO
      1. USCharles John Thompson III
    2. COHello Charles! This will now catch messages you did not explicitly add using the console.* functions. Note, that in order for a message to be caught by this script, it has to be able to be caught by the window.onerror event.
      singulars
      1. PO
      1. USJohn
    3. COSo, it looks like all I needed from your script was the `window.onerror = function...` snippet, as I already have a logging system.
      singulars
      1. PO
      1. USCharles John Thompson III
 

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