Databases
StackOverflow2013
Postsdbo
POLogging Error Code Design, Input needed
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POLogging Error Code Design, Input needed
    primarykey
    data
    text
    <p>So, I'm stuck on a little problem. I was curious if anyone had some extra input they might be willing to give on this design.</p> <p>I have an ILog interface which has two methods exposed for the Error Code logging part of the design. FlagError and GetErrorCode; FlagError sets a bit on an integer, each bit representing that a certain error was thrown., GetErrorCode (which would be the return value for the Main method) returns that said integer.</p> <p>I speculated at first at using an <code>enum</code> in each application to contain a list of possible ErrorCodes.</p> <p>But the problem is, how exactly would I relay to the users that error code 'XYZ' represents that the application hit these un-normal states during execution in a friendly way?</p> <p>ILog Interface: (Write Methods have overloads)</p> <pre><code>interface ILog { void FlagError (int errorCode); int GetErrorCode (); #region Other ILog Methods void WriteError(string message); void WriteWarning(string message); void WriteInfo(string message); void WriteDebug(string message); #endregion } </code></pre> <p>Log Class:</p> <pre><code>abstract class Log : ILog { public void FlagError (int errorCode) { if (errorCode == 0 || errorCode == int.MinValue || errorCode != (errorCode &amp; -errorCode)) { throw new IndexOutOfRangeException (); } if ((m_errorCode &amp; errorCode) == errorCode) return; m_errorCode += errorCode; } public int GetErrorCode () { return m_errorCode; } #region Other ILog Methods } </code></pre> <p>I speculated using an attribute on each enum value with a description of that error, and then just having a little process or something to help 'parse' the error code into a human readable description.</p> <p>But Idk, any Ideas?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMogsdad
    1. USMeiscooldude
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI've seen enums that use switch logic to parse out the descriptions, but my first question is why not use actual specific exceptions for each type of error? If you're not doing that because you are accumulating a set of errors that you want to return, then a bitmasked error code like you describe seems efficient to me. But I personally would use some sort of dictionary of all the errors to pass back. A bitmask, while efficient, is definitely not that easy to read.
      singulars
      1. POLogging Error Code Design, Input needed
      1. USRake36
    2. COIs this what you are trying to do? http://stackoverflow.com/questions/164425/determining-if-enum-value-is-in-list-c
      singulars
      1. POLogging Error Code Design, Input needed
      1. USRake36
    3. COThe problem with returning multiple exceptions, is that some errors can be flagged without an exception actually being thrown and I don't really want to go 'log.FlagError(new AnonException("This Happened"));' But that is a good idea. And no, i'm not trying to do what is in the link. Also, if you want, I would love if you would look over my answer.
      singulars
      1. POLogging Error Code Design, Input needed
      1. USMeiscooldude
 

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