Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Sounds to me like you want a custom <a href="http://msdn.microsoft.com/en-us/library/system.web.mvc.controlleractioninvoker%28v=vs.108%29.aspx" rel="nofollow">ControllerActionInvoker</a> e.g.</p> <pre><code>public class ReadControllerActionInvoker : ControllerActionInvoker { private IMediator mediator; public ReadControllerActionInvoker(IMediator mediator) { this.mediator = mediator; } protected override ActionResult CreateActionResult(ControllerContext controllerContext, ActionDescriptor actionDescriptor, object actionReturnValue) { ViewDataDictionary model = null; // get our query parameter var query = GetParameterValue(controllerContext, actionDescriptor.GetParameters().Where(x =&gt; x.ParameterName == "query").FirstOrDefault()); // pass the query to our mediator if (query is DetailsQuery) model = new ViewDataDictionary(this.mediator.Request((DetailsQuery)query)); // return the view with read model returned from mediator return new ViewResult { ViewName = actionDescriptor.ActionName, ViewData = model }; } } </code></pre> <p>We then introduce a base controller where we inject our custom <code>ControllerActionInvoker</code></p> <pre><code>public class BaseReadController : Controller { protected IMediator Mediator { get; set; } protected override void Initialize(System.Web.Routing.RequestContext requestContext) { base.Initialize(requestContext); ActionInvoker = new ReadControllerActionInvoker(Mediator); } } </code></pre> <p>Then finally in our controller, we derive from our base and return the query information from our actions e.g.</p> <pre><code>public class QueryController : BaseReadController { // our actions now do nothing but define a route for our queries public void About(DetailsQuery query) { } } </code></pre> <p>What you effectively end up with here is bodiless actions so you lose the repetitive code but, in my opinion, you sacrifice some readability (there is a lot of voodoo happening in the controller now which isn't immediately obvious).</p>
    singulars
    1. This table or related slice is empty.
    1. POCan I refactor to Model View Query Handler?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJames
    1. USJames
    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. COSounds interesting, any further advice?
      singulars
      1. PO
      1. USGraemeMiller
    2. CO@GraemeMiller here's an [interesting article](http://weblogs.asp.net/nmarun/archive/2011/02/26/asp-net-mvc-extendable-hooks-controlleractioninvoker-class.aspx) on how you can use it to intercept/control the output for your controller actions. The way I see it, you would end up with a very anaemic controller with nothing but action definitions e.g. `public void Edit(DetailsQuery query) { }` with the mediation stuff sitting in the custom invoker. If I get some time I will try put an example together but if you walk through the article you should find it relatively straightforward.
      singulars
      1. PO
      1. USJames
    3. COWe moved all our logic into queries so was trying to keep the controller as really just a layer over the queries and commands. Make it as thin as possible and really just responsible for coordinating.
      singulars
      1. PO
      1. USGraemeMiller
 

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