Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>My advice, go with Option 1. I use that with all of my Main View/Multiple Partial View scenarios. It's easy to maintain as each partial has it's own ViewModel. It keeps the whole thing nice and clean</p> <p>I use the exact same setup like so:</p> <pre><code>public class MainViewModel { public Partial1ViewModel Partial1 [ get; set; } public Partial2ViewModel Partial2 [ get; set; } public Partial3ViewModel Partial3 { get; set; } public Partial4ViewModel Partial4 { get; set; } public MainViewModel() {} public MainViewModel() { Partial1 = new Partial1ViewModel(); Partial2 = new Partial2ViewModel(); Partial3 = new Partial3ViewModel(); Partial4 = new Partial4ViewModel(); } } </code></pre> <p>Each <code>PartialViewXViewModel</code> is it's own ViewModel and if need be can be reused in another view.</p> <p>Your Action that renders can look like so:</p> <pre><code>public ActionResult Index { var model = new MainViewModel(); return View(model); } </code></pre> <p>Your View</p> <pre><code>@model MainViewModel &lt;div&gt; {@Html.RenderPartial("PartialOne", Model.Partial1)} &lt;/div&gt; &lt;div&gt; {@Html.RenderPartial("PartialTwo", Model.Partial2)} &lt;/div&gt; &lt;div&gt; {@Html.RenderPartial("PartialThree", Model.Partial3)} &lt;/div&gt; &lt;div&gt; {@Html.RenderPartial("PartialFour", Model.Partial4)} &lt;/div&gt; </code></pre> <p>Define the UI for each <code>PartialX</code> like:</p> <pre><code>@model Partial1ViewModel //view html here </code></pre> <p>Now, each Partial view html and each model that they use can be used anywhere. </p> <p>The great part is now if you have a page that needs only 2 of these you just create a new <code>ViewModel</code> to represent that specific view like so:</p> <pre><code>public class OtherMainViewModel { public Partial2ViewModel Partial2 [ get; set; } public Partial4ViewModel Partial4 { get; set; } public OtherMainViewModel() {} public OtherMainViewModel() { Partial2 = new Partial2ViewModel(); Partial4 = new Partial4ViewModel(); } } </code></pre> <p>And use it in another view like so:</p> <pre><code>public ActionResult SomeOtherAction { var model = new OtherMainViewModel(); return View(model); } </code></pre> <p>And that's perfectly acceptable and also the preferred design strategy in MVC, to have ViewModels that specifically represent what a view needs and only what it needs.</p> <p>You may want to use a different method for populating your models tho. Most here would recommend using Automapper. Either way, the above just initializes the PartialViewXModels in the constructor of the MainViewModel. That won't necessarily be your case if you are populating those models with data from your DB. You would want your own strategy for that. This would work here:</p> <pre><code>public ActionResult Index { var model = new MainViewModel(); model.Partial1 = GetPartial1Data(); // this method would return Partial1ViewModel instance model.Partial2 = GetPartial2Data(); // same as above for Partial2ViewModel ... return View(model); } </code></pre> <p>This all would just get you started with the design, you can tweak it to your hearts content :-)</p>
    singulars
    1. This table or related slice is empty.
    1. POMany models to view with many partial views
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCD Smith
    1. USCD Smith
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMany models to view with many partial views
      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. COYou create "MainViewModel" for each page? for example - "MainPageViewModel", "ArticlesPageViewModel" and so on, or you have in every control/page pass the same model and u use what you need? the second option I can understand u can use whatevery property you want, its not over header?
      singulars
      1. PO
      1. USAviran Cohen
    2. COIf you have more than one page that uses all of those partials then yes, you use the ViewModel that that page represents. If you have a page that does not need all of those partials then you create a different ViewModel as seen in my answer update at the end
      singulars
      1. PO
      1. USCD Smith
    3. COThanks, I learned a lot about the MVC perspective of design :)
      singulars
      1. PO
      1. USAviran Cohen
 

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