Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your conventions are pretty standard and quite fine (imho).</p> <p>The one thing to watch is memory fragmentation from excessive unnedded debug calls so, with Log4J (and most other Java logging frameworks), you end up with something like this:</p> <pre><code>if (log.isDebugEnabled()) { log.debug("..."); } </code></pre> <p>because constructing that log message (that you probably aren't using) could be expensive, especially if done thousands or millions of times.</p> <p>Your INFO level logging shouldn't be too "chatty" (and from what you say, it sounds like it isn't). INFO messages should be generally meaningful and significant, like the application being started and stopped. Things that you might want to know if you encounter a problem. Debug/fine level logging is more used for when you actually have a problem you're trying to diagnose. Debug/fine logging is typically only turned on when needed. Info is typically on all the time.</p> <p>If someone doesn't want specific INFO messages from your classes, they are of course free to change your log4j configuration to not get them. Log4j is beautifully straightforward in this department (as opposed to Java 1.4 logging).</p> <p>As for your HTTP thing, I've generally not found that to be an issue with Java logging because typically a single class is responsible for what you're interested in so you only need to put it in one place. In the (rare in my experience) when you want common log messages across seemingly unrelated classes, just put in some token that can easily be grepped for.</p>
    singulars
    1. This table or related slice is empty.
    1. POLogging in Java and in general: Best Practices?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UScletus
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POLogging in Java and in general: Best Practices?
      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. COAs an fyi, in Scala one can write a debug method that does exactly that code without the verbosity using by-name parameters. The compiler automatically converts the code in the debug() argument into a function that is only evaluated if debug() decides to call it. So wouldn't concatenate the string unless the isDebugEnabled() true. Example code that implements this: override def debug(msg: => AnyRef) = if (isDebugEnabled) logger.debug(msg) http://github.com/dpp/liftweb/blob/338119b8d7a76adcb9f45e9aa8a2b946d9c81118/lift-util/src/main/scala/net/liftweb/util/Log.scala
      singulars
      1. PO
      1. USBlair Zajac
    2. COThis is yet another good reason to use the {}-construct provided by slf4j.
      singulars
      1. PO
      1. USThorbjørn Ravn Andersen
 

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