Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I got it to work!</p> <p>For some odd reason, all I needed to do was to pass on the <code>ViewData</code> to a new <code>ResultView</code>. </p> <p>Here's the complete code:</p> <pre><code>public class ErrorLoggingAttribute : ActionFilterAttribute, IExceptionFilter { private String _controllerName, _actionName; private Boolean _redirectToGenericView = false; public ErrorLoggingAttribute() { } public ErrorLoggingAttribute(String actionName, String controllerName) { _controllerName = controllerName; _actionName = actionName; _redirectToGenericView = true; } void IExceptionFilter.OnException(ExceptionContext ec) { // log error if (_redirectToGenericView) { ec.Result = new RedirectToRouteResult(new RouteValueDictionary { {"controller", _controllerName}, {"action", _actionName} }); } else { ec.Result = new ViewResult { ViewName = ((RouteData) ec.RouteData).Values["action"].ToString(), TempData = ec.Controller.TempData, ViewData = ec.Controller.ViewData }; } ec.ExceptionHandled = true; } } </code></pre> <p><br /></p> <h2>Usage</h2> <p><br /> Here's how you would use the attribute on a controller-action, to redirect to the same view (<em>with</em> it's associated model) to enable standard validation-helpers to kick in, when an exception occurs:</p> <pre><code>[ErrorLogging] [AcceptVerbs(HttpVerbs.Post)] public ActionResult Create(Models.Entities.Message message) { var dc = new Models.DataContext(); dc.Messages.InsertOnSubmit(message); dc.SubmitChanges(); return RedirectToAction("List", new { id = message.MessageId }); } </code></pre> <p>And here's how you would use the attribute, to redirect to a generic view, when an exception occurs:</p> <pre><code>[ErrorLogging("ControllerName", "ViewName")] [AcceptVerbs(HttpVerbs.Post)] public ActionResult Create(Models.Entities.Message message) </code></pre> <p><br /> This is a <em>complete</em> separation of logic. Nothing in the controller but the very basics.</p>
    singulars
    1. This table or related slice is empty.
    1. POReturning a view with it's model from an ActionFilterAttribute
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USroosteronacid
    1. USroosteronacid
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POReturning a view with it's model from an ActionFilterAttribute
      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. VTAcceptedByOriginator
    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. COYour controller should be focussed on application flow, using this approach obscures the logical application flow by shifting the error portion of it up into attributes. Just because you can, doesn't mean you should.
      singulars
      1. PO
      1. USNeal
    2. COThat's great. Was struggling with this for days. Had to modify my code a bit, though. I user partial views which are rendered via jQuery ajax. Now the controller is completeley free of try catch final. ((RouteData) ec.RouteData).Values["action"].ToString() returns the name of the view, but i needed the name of the partial view.
      singulars
      1. PO
      1. USzszep
 

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