Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would absolutely not use WCF purely on the basis of architecture, unless you specifically needed features it provided. I.e. certain transports/protocals to support certain business to business needs. MVC has WebAPI now which is basically same stuff migrated from WCF and made much easier to use, and might meet your architectural needs with much less headache.</p> <p>Additionally, I would not even use WebAPI unless I was exposing a something that I know for sure will be used outside of my application. If this service layer will only be used by this MVC application, then I would do away with it. You can still have a business layer+data layer and maintain separation of concerns without it. That's just my own opinion.</p> <p>Usually I make use of View Models, which are models tailored for the view. They allow me to refactor either the View or the database independently and only have to change the data transformation code. I.e. database field changed might only require a tweak in the query, and the ViewModel stays the same, thus all views using that view model stay the same. Pretty much the same way you are querying and transforming the entities from the query into a <code>new Account</code> except I name mine AccountVM for view model(the <strong>model</strong> specifically for the <strong>view</strong>)</p> <p>I personally call these types of data query/transformation methods from my controller. The controller then just passes the AccountVM or collection to the <code>View(vm)</code> where vm is the name of the variable holding the AccountVM or collection.</p> <p>This is how I get the data from DB to View. The EF entity classes and VM classes are usually pretty similar anyhow, and sometimes identical. I feel like a middle business entity class would be too similar to one or the other to really warrant the extra class and extra copying.</p> <p>So to answer a couple of your questions in my opinion: 1 Yes, basically I think this is a good approach.</p> <p>2 This GetAccountAndItsTraits is called from the Controller and the View is based on your business poco(or what I call ViewModel). So the return from the business layer matches what your model expects. I wouldn't have a service layer here. However, I might instead have some methods dedicated purely to converting EF entities to View Models, which would happen after the business model function is called. In other words, the business model would return EF entities, and then mapping functions would map those to whatever view model is needed in that case, since you could have lots of View Models and Views that utilize that same business method. I use EF Code First, so my entity classes are already pretty close to being POCOs, so it doesn't offend me for them to leak into other layers.</p>
    singulars
    1. This table or related slice is empty.
    1. POASP.NET MVC - Service Layer - Business Layer - Data Layer (EF) - SQL DB :: Data Transfer?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAaronLS
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis is essentially the approach I use too. I would add that Automapper takes a lot of the work out of mapping EF entities to ViewModels.
      singulars
      1. PO
      1. USPaul Taylor
    2. COYes I was going to suggest that, but AutoMapper can be daunting. I'd probably not use for awhile and get a feel for everything else for awhile, and then start using AutoMapper gradually.
      singulars
      1. PO
      1. USAaronLS
    3. CO@AaronLS Thanks for your reply. I have to use WCF is because my business tier is in separate physical box. I use WebAPI to communicate between the View ( client browser ) to UI server ( Controller) and the Controller from UI server would have to call WCF to access the business services. I need to apply my business logic on business Models in my business layer and not the ViewModel.
      singulars
      1. PO
      1. USKarthik
 

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