Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>My 2 cents worth:</p> <ul> <li>Use a common top-level namespace so everything that's part of your framework can be easily identified. You might not "need" it but it just seems silly not to.</li> <li>Use descriptive names. Things like <code>Basti.SpecialFramework.Interfaces.DataAccess.Customer</code> would make a lot of sense to me.</li> <li>Structuring the namespace around the structure / architecture of your system makes <strong>lots</strong> of sense.</li> <li>Having a well structured namespace tree will help the interpretation of key works / terms in the same place, e.g: <code>Basti.SpecialFramework.Interfaces.DataAccess.Customer</code> vs <code>Basti.SpecialFramework.BaseImplementations.DataAccess.Customer</code></li> <li>Treat it a bit like developing Information Architecture or doing usability testing: come up with a draft set of names and see if your friends can figure it out. Do the eqivalent of a <a href="http://en.wikipedia.org/wiki/Card_sorting" rel="nofollow">Card Sorting</a> exercise - do you structure it: [Layer].[Interface / BaseImplementation] or [Interface / BaseImplementation].[Layer]? (I'm not sure exactly how you would do the card sorting exercise but I can see some strong parallels).</li> <li>Descriptive names tend to be long, this goes aganist your last point; I agree long names might not be "easy" and "convenient" but if they clearly convey what I need to know I would be okay with that.</li> </ul> <p>By the way: I'm sure naming conventions exist for DLLs and Assembilies - I just don't know them off the top of my head. I guess I could Google / Bing them but I guess you've done that already.</p>
    singulars
    1. This table or related slice is empty.
    1. POC# .net - Dll Naming Conventions in Interface / Implementation Scenarios
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAdrian K
    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. This table or related slice is empty.
    1. This table or related slice is empty.
 

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