Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Class names like InvoiceReader, PriceCalculator, MessageBuilder, ArticleReader, InvoiceReader are not actually verb names. They are really "noun agent-noun" class names. See <a href="http://en.wikipedia.org/wiki/Agent_noun" rel="noreferrer">agent nouns</a>.</p> <p>A verb class name would be something like Validate, Operate, Manage etc. Obviously these are better used as methods and would be quite awkward as class names.</p> <p>The biggest problem with "noun agent-noun" class names is that they can give very little meaning as to what the class actually does (eg UserManager, DataProcessor etc). As a result they are more likely to be bloated and to lose internal cohesion. (See <a href="http://en.wikipedia.org/wiki/Single_responsibility_principle" rel="noreferrer">Single Responsibility Principle</a>).</p> <p>Therefore the WebService class with the IInvoiceReader and IArticleReader interfaces is probably the clearer and more meaningful OO design.</p> <p>This gives you the simple, obvious noun class name "WebService", along with "noun agent-noun" interface names that clearly advertise what the WebService class can do for callers.</p> <p>You could probably also give more meaning to the actual class by prefixing another noun, for example PaymentWebService. </p> <p>However the interfaces are always better than a single class-name at describing more specifically what the class can do for callers. As the class grows more complex, new interfaces can also be added with meaningful names. </p>
    singulars
    1. This table or related slice is empty.
    1. POClasses to avoid (code complete)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAsh
    1. USAsh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POClasses to avoid (code complete)
      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. COI agree with everything you've said here, although the examples in the book do refer to agent nouns like `StringBuilder` (ironic that the .NET Framework literally has this exact class). `InvoiceReader` tells me a lot more about the purpose of the class than `WebService`.
      singulars
      1. PO
      1. USAaronaught
    2. CO@Aaronaught, yes I'd probably use a more specific name than WebService such as PaymentWebService to give more meining. However the Interfaces are the key part to describing what the class does. They can do this much more accurately and at more granular level, even more so as the class grows in size (ie more interfaces can be added).
      singulars
      1. PO
      1. USAsh
    3. CO@Jeff, yes it's probably most important to get consensus where you work as to the naming approach and then stick with it. ie consistency which ever naming style is used.
      singulars
      1. PO
      1. USAsh
 

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