Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><code>ASP.NET MVC</code> layer or tier doesn't contains neither business logic nor business model. <code>M</code> in <code>MVC</code> stands for UI model, not the model of your application core and <code>MVC</code> (as well as other <code>MV*</code> patterns) is generally pattern for separating UI concerns. You should send messages (call) your Business Layer (BL) from Controllers, aggregate data, create or map it results into UI model and pass it to view. Your UI model should know nothing of BL model - this distinction makes loosely coupled layers of your application. </p> <blockquote> <p>In other words we can say from where I need to call my middle layer. From the Models or from the Controllers?</p> </blockquote> <p>Definitely from Controllers. You inject dependencies to it and call them from your Action methods. ASP.NET MVC provide lots of mechanisms of injection dependencies into controllers and integrates nicely with NInject, StructureMap and some other IoC containers.</p> <p>Dependencies between components in MVC is given below</p> <p><img src="https://i.stack.imgur.com/YTC16.png" alt="enter image description here"></p> <p>Picture is takes from Martin's Fowler article on <a href="http://martinfowler.com/eaaDev/uiArchs.html" rel="nofollow noreferrer">GUI Architecture</a>, which by the way, very nice reading regarding MVC and MVP. </p> <p>Also, <a href="http://www.pluralsight.com/training/Courses/TableOfContents/patterns-library" rel="nofollow noreferrer">Pluralsight</a> has set of videos on Software Practices, which covers Design Patterns. I've learned a lot from their definition of MVVM and MVP. </p> <p>Reading this materials should increase your understanding not only on patterns itself, but also in how they fit into application environment and interact with it. </p>
    singulars
    1. This table or related slice is empty.
    1. POUsing MVC Pattern With 3 Layer Architecture
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USIlya Ivanov
    1. USIlya Ivanov
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUsing MVC Pattern With 3 Layer Architecture
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks a lot Ilya Ivanov. Your really helped me. one thing I forgot to ask that where do we perform presentation validation? In the view or in the controller.
      singulars
      1. PO
      1. USUzair Anwaar
    2. COCan you please explain in a little bit more detail what do you mean by presentation validation? User input? It should be triggered by controllers but it's is better to place logic near the data, on which this validation in executed. So model seems to be a good place. But this can vary depending on the context of the problem.
      singulars
      1. PO
      1. USIlya Ivanov
    3. COYes I want to validate user input. You said Model is a good place to do but what about client side validation? If we put validation in Model it requires post back or if we put validation on both places model and view the code is isolated in two different places for the same concern can cause problem to maintain may hard to maintain
      singulars
      1. PO
      1. USUzair Anwaar
 

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