Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You should take a look what <a href="http://tekpub.com/view/concepts/1" rel="nofollow noreferrer">dependency injection</a> and inversion of control in general means. That would provide ability to control life cycle of <code>ObjectContext</code> "from outside". You could ensure that only 1 instance of object context is used for every http request. To avoid managing dependencies manually, I would recommend using <a href="http://dotnetslackers.com/articles/designpatterns/IntroductionToStructureMap.aspx" rel="nofollow noreferrer">StructureMap</a> as a container.</p> <p>Another useful (but quite tricky and hard to do it right) technique is abstraction of persistence. Instead of using <code>ObjectContext</code> directly, You would use so called <a href="http://martinfowler.com/eaaCatalog/repository.html" rel="nofollow noreferrer">Repository</a> which is responsible to provide collection like API for Your data store. This provides useful <em>seam</em> which You can use to switch underlying data storing mechanism or to mock out persistence completely for tests.</p> <p>As Jason suggested already - You should also use <a href="https://stackoverflow.com/questions/2478081/entity-framework-4-poco-where-to-start">POCO`s</a> (plain old clr objects). Despite that there would still be implicit coupling with entity framework You should be aware of, it's much better than using generated classes.</p> <p>Things You might not find elsewhere fast enough:</p> <ol> <li>Try to avoid usage of <a href="https://stackoverflow.com/questions/4425750/should-a-repository-implement-unitofwork/4428982#4428982">unit of work</a>. Your model should define transactional boundaries.</li> <li>Try to avoid usage of <a href="https://stackoverflow.com/questions/1230571/advantage-of-creating-a-generic-repository-vs-specific-repository-for-each-objec/1231473#1231473">generic repositories</a> (do note point about IQueryable too). </li> <li>It's not mandatory to spam Your code with <a href="http://fragmental.tw/2010/12/23/how-to-write-a-repository/" rel="nofollow noreferrer">repository pattern name</a>.</li> </ol> <p>Also, You might enjoy reading about <a href="http://rads.stackoverflow.com/amzn/click/0321125215" rel="nofollow noreferrer">domain driven design</a>. It helps to deal with complex business logic and gives great guidelines to makes code less procedural, more object oriented.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs DTO plus UnitOfWork pattern a good approach to design a DAL for a web application?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USArnis Lapsa
    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. COplease look question's last version... thanks!
      singulars
      1. PO
      1. USJPCF
    2. CODo you have example of DDD with EF - I'm especially interested how do you define transactional boundaries.
      singulars
      1. PO
      1. USLadislav Mrnka
    3. CO@Ladislav unfortunately, I'm not too familiar with EF. kind a blindly believing that NHibernate is still superior. but that would change only repository part. transactional boundaries are drawn by aggregate roots themselves because they are responsible for valid state and are persisted in atomic operation. correct modeling of them are the key.
      singulars
      1. PO
      1. USArnis Lapsa
 

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