Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have actually been struggling with something like this quite a bit at work.</p> <p>It was based on an <a href="http://codeblog.jonskeet.uk/2006/01/05/classenum/comment-page-1/#comment-9575" rel="nofollow noreferrer">example that was posted by John B</a> in <a href="http://codeblog.jonskeet.uk/2006/01/05/classenum/" rel="nofollow noreferrer">Jon Skeet's blog article "Enhanced enums in C#"</a>.</p> <p>What I did not get to work properly without a LOT of ugliness was extending an enumeration by deriving a base enumeration class and adding additional static fields of the deriving type. </p> <p>If you check the basics that are posted in that blog you'll notice that deriving classes will share a common set of values which have serious typing issues and when a certain enumeration base class is derived in two different other classes their value sets will be in the same collection too.</p> <p>I mean, you'd be hard pressed to create a variable of DerivedEnumClass1 and having to store a value from it's enumeration collection which is actually of type BaseEnumClass1 in that variable without workarounds.</p> <p>Another problem was Xml Serialization which we use a lot. I got around that using two generic classes as datatypes on enumeration variables on our business objects: one that represented a single enumeration value and one that represented a set of enumeration values which I used to mimic flags enumeration behaviour. They handled xml serialization and deserialization of the actual values that were stored in the properties they were representing. A couple operator overloads were all that was necessary to recreate bitflag behaviour this way.</p> <p>Those are some of the major issure I ran into.</p> <p>All in all I'm not very pleased with the end result, some smelly stuff in there but it does the job for now.</p> <p>Why our chief architect decided to still try and get it to work was the possibilities of having actual classes and extending them with all kinds of behaviour, either generic or specific. Thus far I have not seen a lot I wouldn't have been able to provide with extension methods, but we might run into something.</p> <p>Don't have any of the code here and I'm not gonna be able to get to it for the weekend otherwise I could have shown where I had gone with it. Not very pretty though... :o</p>
    singulars
    1. This table or related slice is empty.
    1. POWhen to use enums, and when to replace them with a class with static members?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USstakx
    1. USAnton
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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
    1. COInteresting blog article that you linked to! -- One thing that I was a little concerned about with the enum-as-class approach was that the code for a simple `enum` looks much nicer. Implementing an enum as a class can complicate the code a lot, and IMHO perhaps the point at which it gets **too** complicated is quickly reached?
      singulars
      1. PO
      1. USstakx
    2. COThe code for the actual enums themselves is not that complicated at all. You have the generic class to put all basic functionality in that you require from your expanded enumerations. The enumerations themselves then boil down to no more than the static fields and a private constructor. Plus any specific functionality for that one enum. I spent most of the time on allowing developers to use them like regular enumerations/bit flags. But yeah, you'd better have a very good reason to start using enums like this.
      singulars
      1. PO
      1. USAnton
 

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