Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>If you are looking for object-relational mapping models you can look into:</strong></p> <ul> <li><a href="http://en.wikipedia.org/wiki/NHibernate" rel="nofollow noreferrer">NHibernate</a></li> <li><a href="http://en.wikipedia.org/wiki/LLBLGen" rel="nofollow noreferrer">LLBLGen</a></li> <li><a href="http://en.wikipedia.org/wiki/IBATIS" rel="nofollow noreferrer">iBATIS</a></li> </ul> <p>There's also a longer list here: <a href="http://en.wikipedia.org/wiki/List_of_object-relational_mapping_software#.NET" rel="nofollow noreferrer">http://en.wikipedia.org/wiki/List_of_object-relational_mapping_software#.NET</a></p> <p><strong>As for the general question of how to design an object model for persistence,</strong> much of the design choice depends on the complexity of the system, the extensibility you require, whether you need to support multiple persistence stores (SQLServer, Oracle, file system, etc), and so on. The pattern you describe looks like a <a href="http://msdn.microsoft.com/en-us/library/ms978717.aspx" rel="nofollow noreferrer">DataTansferObject (DTO)</a>. It's a common design for separating persistence logic from business logic.</p> <p><strong>As an aside, a general principle of good system design is the <a href="http://en.wikipedia.org/wiki/Single_responsibility_principle" rel="nofollow noreferrer">single responsibility principle</a>.</strong> When building a system, you have to decide whether it makes sense to combine different responsibilities into a single class. Combining responsibilities can often complicate a system and create design conflicts that are difficult to resolve.</p>
    singulars
    1. This table or related slice is empty.
    1. PO.NET Object persistence options
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USLBushkin
    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. COJust want to add SubSonic to the list http://www.subsonicproject.com/
      singulars
      1. PO
      1. USDevelopment 4.0
    2. COThanking you for putting a name on rather long winded description :). Do you think that the type of mapping models you've described are suitable for coming in late in a products life cycle (as in my case), or are they more suited to ground up development?
      singulars
      1. PO
      1. USMrEdmundo
    3. COIt depends. Some libraries are better at working with POCOs, others are not. Libraries that that require the consumer to implement numerous interfaces or inherit from specific base classes are clearly harder to introduce into a project late in the game. NHibernate, for example, is relatively good at working with POCOs - so you may be able to use it even late in a project. However, keep in mind - there is something to be said for consistency of implementation. Having multiple different ways to persist data in an application may not be conducive to long-term maintenance or developer on-boarding.
      singulars
      1. PO
      1. USLBushkin
 

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