Databases
StackOverflow2013
Postsdbo
PODesign pattern for class with upwards of 100 properties
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODesign pattern for class with upwards of 100 properties
    primarykey
    data
    text
    <p>What advice/suggestions/guidance would you provide for designing a class that has upwards of 100 properties?</p> <p><strong>Background</strong></p> <ul> <li>The class describes an invoice. An invoice can have upwards of 100 attributes describing it, i.e. date, amount, code, etc...</li> <li>The system we are submitting the invoice to uses each of the 100 attributes and is submitted as a single entity (as opposed to various parts being submitted at different times).</li> <li>The attributes describing the invoice are required as part of the business process. The business process can not be changed.</li> </ul> <p><strong>Suggestions?</strong></p> <ul> <li>What have others done when faced with designing a class that has 100 attributes? i.e., create the class with each of the 100 properties? </li> <li>Somehow break it up (if so, how)? </li> <li>Or is this a fairly normal occurrence in your experience?</li> </ul> <p><strong>EDIT</strong> After reading through some great responses and thinking about this further, I don't think there really is any single answer for this question. However, since we ended up modeling our design along the lines of <a href="https://stackoverflow.com/questions/1633196/design-pattern-for-class-with-upwards-of-100-properties/1633256#1633256">LBrushkin's Answer</a> I have given him credit. Albeit not the most popular answer, LBrushkin's answer helped push us into defining several interfaces which we aggregate and reuse throughout the application as well as a nudged us into investigating some patterns that may be helpful down the road.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USMetro Smurf
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODesign pattern for class with upwards of 100 properties
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODesign pattern for class with upwards of 100 properties
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODesign pattern for class with upwards of 100 properties
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHow are you serializing/deserializing the objects - do you store them in a database? Are you using WCF?
      singulars
      1. PODesign pattern for class with upwards of 100 properties
      1. USPhilip Wallace
    2. CO@Philip - the data is stored in a combination of SharePoint and SQL Server. No WCF. All submission of data is done between internal systems where the end point takes an Excel spreadsheet of the data (no other options with the system).
      singulars
      1. PODesign pattern for class with upwards of 100 properties
      1. USMetro Smurf
    3. COAre you actually dealing with all (or most) of those properties in your code? Or is it just a data structure that "passes through" it - read from some input in a generic fashion, just to be output to some other existing software that implements your business process?
      singulars
      1. PODesign pattern for class with upwards of 100 properties
      1. USPavel Minaev
 

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