Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think you are heading in the right direction about the Repository pattern. Regarding your question about the ViewModel classes, i suggest that you use something that transforms the output of the business service method outputs to some desired outputs. For example your Order business service may have a method called <code>GetOrders()</code>. Using a custom attribute you may define the view class type for it. The view is able to get the output of this method, possibly joins it with other kinds of data and returns the result as a collection of objects with anonymous types. In this case the view will take <code>IQueryable&lt;Order&gt;</code> or <code>IEnumerable&lt;Order&gt;</code> as input and returns <code>IList</code> as the output.</p> <p>This method will help you greatly when you need to show different kinds of views of your data on the client side. We have already utilized something similar (but more complex) to this method in our company's framework.</p>
    singulars
    1. This table or related slice is empty.
    1. POSeparation of Concerns the Repository Pattern & Entity Framework 3.5
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USred.clover
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSeparation of Concerns the Repository Pattern & Entity Framework 3.5
      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. VTAcceptedByOriginator
    1. COThanks for the feedback. This suggestion sounds very interesting. Are you basically saying that I could create a custom attribute that will provide another way of looking at the data...just like a view? If that is the case, can you point me in the right direction for this concept. Sounds like it could be a great idea. Also, when the repository returns DTO objects, they are generally the same name as the EF generated objects...would you suggest just using a different naming convention for the DTOs to avoid type conflicts?
      singulars
      1. PO
      1. USCraig
    2. COOne way I do it is to create a ViewModel per View. Where the ViewModel classes are just aggregates of the data I want to display. I don't see any problem with moving the ORM Entities thru these ViewModels, but if that makes you uncomfortable, you can always just put the ORM models in another assembly, and make them private. Then use something like StuctureMap to transform them into your ViewModel and it's data.
      singulars
      1. PO
      1. USKris
    3. COCustom attribute will give you the ability to define different possible view models for business service methods. Thus those method's output will be fed to the view model and it will take care of generating the desired output. To implement this behavior you'll need a proxy class for the business service that calls the desired method, extracts the appropriate view name from meta data, passes the business output to the view then returns the view output.
      singulars
      1. PO
      1. USred.clover
 

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