Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you need this 'common data' across all views, I would not throw inheritance in the mix. I would go for an extension method.</p> <p>Something along the lines of:</p> <pre><code>public static CommonData GetCommonData(this HtmlHelper htmlhelper) { // do your magic here } </code></pre> <p>In your View you could then simply call:</p> <pre><code>@Html.GetCommonData()... </code></pre> <p>That way you keep your models cleaner.</p> <p>Inheritance might be a valid approach, if this Common Data really 'fits' well with your Model classes.</p> <p>It would help if you provided some examples ;-)</p> <p>** EDIT **</p> <p>I would keep your 'BaseModel' as a property in the Controller and populate it on OnActionExecuting as you suggest.</p> <p>But I would use ExtensionMethods on the Controller and Html helper to access the the data. If you use inheritance you will needlessly complicate things.</p> <p>Let me know if you need samples of the extension methods.</p> <p>This approach is DRY. You are not duplicating code.</p> <p>** EDIT 2 **</p> <p>Here is how your extension method should look like: (off the top of my head, so it might not compile)</p> <pre><code>public static class ExtensionHelpers { public static BaseModel GetCommonData(this HtmlHelper htmlhelper) { YourController HtmlHelper = htmlhelper.ViewContext.Controller as YourController; if (controller != null) { return HtmlHelper.BaseModel; } return null; } </code></pre> <p>Make sure the Controller derives from the Controller class where you add the BaseModel property. I called it 'YourController' above.</p> <p>Then you should be good to go ;-)</p> <p>Edit 3</p> <p>Just a reminder that the namespace needs to be known if you want to use extension methods in a View. The best way to achieve this is to include the namespace in the Web.Config in your Views folder.</p> <pre><code> &lt;system.web.webPages.razor&gt; &lt;host factoryType="System.Web.Mvc.MvcWebRazorHostFactory, System.Web.Mvc, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /&gt; &lt;pages pageBaseType="System.Web.Mvc.WebViewPage"&gt; &lt;namespaces&gt; &lt;add namespace="System.Web.Mvc" /&gt; &lt;add namespace="System.Web.Mvc.Ajax" /&gt; &lt;add namespace="System.Web.Mvc.Html" /&gt; &lt;add namespace="System.Web.Routing" /&gt; &lt;add namespace="Yournamespace" /&gt; &lt;- LOOK HERE &lt;/namespaces&gt; &lt;/pages&gt; &lt;/system.web.webPages.razor&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODerive Model from Another Model
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USsantiagoIT
    1. USsantiagoIT
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODerive Model from Another Model
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI know, I know... I couldn't think of any useful example at the time. I think I've addressed it well though in my recent updating above. The bottom line is that I need to access strongly typed properties on most of my models but in the spirit of DRY, I wanted to keep the code to populate those properties in one place (a base controller, I think).
      singulars
      1. PO
      1. USbeaudetious
    2. COI better understand now. I will update my answer
      singulars
      1. PO
      1. USsantiagoIT
    3. COAdded even more detail (I hope) in my initial posting. Thanks for the gentle reminder.
      singulars
      1. PO
      1. USbeaudetious
 

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