Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I agree with @Tim that you should use a single controller. A controller is a logical grouping of actions; for example the CRUD operations for Foo. <a href="http://nerddinner.codeplex.com/" rel="nofollow">NerdDinner</a> is a good example of this.</p> <p>I disagree with the routes. You can do whatever you want with the routing; but it should be meaningful to the user. You probably just have a single catchall route similar to the one below.</p> <pre><code> routes.MapRoute("Default", //RouteName "{controller}/{action}/{id}", //RouteUrl new { //RouteDefaults controller = "Home", action = "Index", id = UrlParameter.Optional} ) </code></pre> <p>You can have the routes you want by using a single controller.</p> <p>Your desired urls:</p> <blockquote> <p>myapp/Home<br> myapp/Summary/prop1/prop2<br> myapp/Detail/prop1/prop2/prop3</p> </blockquote> <p>The controller setup:</p> <pre><code>public class HomeController : Controller { public ActionResult Index() { ... } public ActionResult Summary() { ... } public ActionResult Details() { ... } } </code></pre> <p>The routing setup:</p> <pre><code> routes.MapRoute("Home-Index", //RouteName "myapp/Home", //RouteUrl new { //RouteDefaults controller = "Home", action = "Index"}); routes.MapRoute("Home-Summary", //RouteName "myapp/Summary/prop1/prop2", //RouteUrl new { //RouteDefaults controller = "Home", action = "Summary", prop1 = UrlParameter.Optional, prop2 = UrlParameter.Optional}); routes.MapRoute("Default", //RouteName "{controller}/{action}/{id}", //RouteUrl new { //RouteDefaults controller = "Home", action = "Index", id = UrlParameter.Optional} ) </code></pre> <p>Now there are a few important things to note:</p> <ol> <li><p>Routing works like a switch statement, the first url that matches is the one it will use, that's why you have the catchall as the last one.</p></li> <li><p>The url defined in your map route can be whatever you want. It doesn't have to match with the controller, because once you remove the placeholders ({controller}, etc) it uses the default for navigation. So the Home-Index route url could be myapp/foo/bar/baz and id would still take you to the Home index action.</p></li> <li><p>The placeholders work automagically. I have not been able to find a good resource explaining how the default route works.</p></li> </ol> <p>Hope this helps.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to name/divide controllers in MVC3 application
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USdrneel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to name/divide controllers in MVC3 application
      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
    1. COI think this matches my requirements: It seemed madness to have multiple controllers OR have a URL that had "Home" in it every time, when this wasn't necessary and didn't add any value.
      singulars
      1. PO
      1. USBlueChippy
    2. COIf you go down this path your routing will get too complex. Best practice is to use the standard routing where possible and create a different controller for each. That way your page names map directly to your folder structure
      singulars
      1. PO
      1. USDaveo
    3. CO@Daveo I agree that you would normally want to use the default routing. I disagree that creating new controllers for the sake of routing is best practice. For example, it doesn't make sense to create a new controller for each piece of CRUD functionality, just so you can have custom routes. Additionally, while creating custom routes can become complex, I would rather have multiple routes in a single location instead of a multitude of controllers which have related code spread among them.
      singulars
      1. PO
      1. USdrneel
 

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