Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I always consider logging from the start. </p> <p>Firstly there is the decision of which logging framework to use, but that is generally a quick choice. I personally often use log4net, which means each class uses the static LogManager.GetLogger to get an instance of a logger. The actual behaviours of each log call is then defined in config (where should I log too, what level should I log at, etc).</p> <p>However, more importantly, you should be thinking of <em>what needs logging</em> as you are actually developing your application. There is no point at which you are more tuned into your code than when you are writing it, and you probably have a better idea of what needs logging then than at any other time. It is far easier to retrospectively remove overly verbose logging that you don't need that add logging that should be there.</p> <p>So yes - always think about logging as you start your application, don't try and retro-fit it if you can help it.</p> <p><strong>[EDIT: In response to your question about how to inject]</strong></p> <p>Possibly the simplest approach (assuming you are not using an IoC container) is to go down the route of property or constructor injection. Personally, I much prefer the latter for this sort of thing, so I would end up with something like this for log4net:</p> <pre><code>public class MyClass { private readonly ILog _logger; // usually I don't supply a logger directly, // hence I let this ctor get a logger from the log manager. public MyClass() : this (LogManager.GetLogger(typeof(MyClass))) { } // this ctor only gets called directly if I want to mock out logging public MyClass(ILog logger) { _logger = logger; } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODesign for logging or adding logging afterwards?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRob Levine
    1. USRob Levine
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODesign for logging or adding logging afterwards?
      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. COIsn't a static bad for testing? How would you mock it? or would you just have a special configuration for when testing?
      singulars
      1. PO
      1. USRodi
    2. CO@Rodi - you're absolutely right - in fact what I said above is a simplification of what I really do, for brevity's sake. The logger itself in log4net is of type ILog, and so this can be mocked and injected in using an IoC, or accessed via a "lazy-load" property that only calls the LogManager.GetLogger if a mock logger has not already been supplied.
      singulars
      1. PO
      1. USRob Levine
    3. COHave you got an example or a link to one somewhere? Thanks.
      singulars
      1. PO
      1. USRodi
 

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