Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Optional segments can only be placed at the end of your route or better <strong>after required ones</strong>. That's why you have to add an additional route definition without <code>id</code> segment that also defines its default as <code>0</code>.</p> <h2><code>id</code> is numeric</h2> <pre><code>public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.IgnoreRoute("{*favicon}", new { favicon = @"(.*/)?favicon.ico(/.*)?" }); routes.MapRoute( "Default", "{id}/{controller}/{action}", new { controller = "Home", action = "Index" }, new { id = @"\d+" } ); routes.MapRoute( "DefaultId", "{controller}/{action}", new { controller = "Home", action = "Index", id = "0" } ); } </code></pre> <p>As you can see, the first route definition also includes a constraint for the <code>id</code> segment which makes a requirement for it to be numeric. That's the trick.</p> <h2><code>id</code> is alphanumeric but not matching any controller name</h2> <p>In case <code>id</code> is not numeric but can be alpha numeric then you will have to take a different approach...</p> <pre><code>public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.IgnoreRoute("{*favicon}", new { favicon = @"(.*/)?favicon.ico(/.*)?" }); routes.MapRoute( "DefaultId", "{controller}/{action}", new { controller = "Home", action = "Index", id = "0" }, new { controller = @"Home|Admin|Categories|Items" } ); routes.MapRoute( "Default", "{id}/{controller}/{action}", new { controller = "Home", action = "Index", id = "0" } ); } </code></pre> <p>Then you will have to put a constraint on the <code>controller</code> segment, because you have a finite number of them. Mind that route definitions have swapped so the id-less one is now the first and the one with the <code>id</code> is now second. This should work as long as <code>id</code> can never have the same value as controller name.</p> <h2><code>id</code> can be anything really</h2> <p>But what if <code>id</code> can have a value equal to a controller name? Well in that case you will have to define your routing rules a bit more strictly because you will most likely have to omit default values and provide more routes based on number of segments: zero, one, two, three or even more if required.</p>
    singulars
    1. This table or related slice is empty.
    1. POPossible to setup a {id}/{controller}/{action} route with null {id}?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRobert Koritnik
    1. USRobert Koritnik
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPossible to setup a {id}/{controller}/{action} route with null {id}?
      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. COWhat if `id` were alphanumeric of indeterminate length, like a slug? I tried using `@"\[a-zA-Z0-9]+"` but that didn't work
      singulars
      1. PO
      1. USMike
    2. CO@Mike: See my edited answer.
      singulars
      1. PO
      1. USRobert Koritnik
    3. COAwesome! This works exactly how I needed. Thanks!
      singulars
      1. PO
      1. USMike
 

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