Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I like to keep the URLs as logical as possible, and avoid framework-specific URLs (consider that you may change the framework in the future, which would then have to keep using your old URL patterns to avoid breaking external links.)</p> <p>Basically:</p> <pre><code># All customers: /customers/ # New customer: /customers/new /customers/?new # another version if you don't think "new" deserves its own path # Existing customer: /customers/123/ /customers/123 # another version if you want the concept that it's a page, not a # directory # Edit customer: /customers/123/edit /customers/123?edit # Some sub-list for a customer: /customers/123/orders/ # and so on... </code></pre> <p>To be honest, I personally prefer the second example in the cases where I provided two examples. It uses the concept from file systems that lists are "directories" and separate entries are "files". Every path represents some kind of data, and other paths are separated using the query string (<code>/customers/?new</code>).</p> <p>After you've decided on your URL structures, you should have a look at how to implement this in your web framework. Most frameworks I consider "good" have some kind of support for mapping URLs (usually with some kind of pattern supporting wildcards, such as regular expressions.) So your patterns might look like this, using my second examples (regex):</p> <pre><code>^/customers/$ -&gt; CustomerList ^/customers/(\d+)$ -&gt; Customer # This will check the query string for "edit" etc # to determine which mode to use. ^/customers/(\d+)/orders/$ -&gt; OrderList </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POBest way to define your web application URLs
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBlixt
    1. USBlixt
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBest way to define your web application URLs
      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
    1. COYour answer helped me clarify that the best strategy for my "need" is no longer relevant. Having a base url for each given page doesn't make sense anymore. Thanks for the clear perspective.
      singulars
      1. PO
      1. USscunliffe
 

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