Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think, the better way is to add the same view twice with difference renderers. Suppose we have the following view:</p> <pre><code>def my_view(request): return {"message": "Hello, world!"} </code></pre> <p>Now in our configuration we can add the same view twice:</p> <pre><code>from pyramid.config import Configurator config = Configurator() config.add_route('test', '/test', my_view, renderer="templates/my_template.mako") config.add_route('test', '/test', my_view, renderer="json", xhr=True) </code></pre> <p>What we have now:</p> <ol> <li>View <code>my_view</code> will render template <code>"templates/my_template.mako"</code> with returned dict provided as context if we will point our browser to url <code>/test</code>.</li> <li>If we will make XHR request with <code>my_view</code> will be called again, but now returned dict will be encoded as JSON and transmitted back to caller (please <a href="http://docs.pylonsproject.org/projects/pyramid/en/latest/api/config.html#pyramid.config.Configurator.add_view" rel="noreferrer">read docs</a> about checking if request was done via XHR).</li> </ol> <p>The same idea we can use for defining different routes but with the same view attached to them:</p> <pre><code>from pyramid.config import Configurator config = Configurator() config.add_route('test', '/test', my_view, renderer="templates/my_template.mako") config.add_route('test_json', '/test.json', my_view, renderer="json") </code></pre> <p>Now <code>/test</code> will trigger template rendering, but <code>/test.json</code> will return just JSON encoded string.</p> <p>You can go further and make dispatching to the right renderer via <code>accept</code> argument of <code>add_router</code> method:</p> <pre><code>from pyramid.config import Configurator config = Configurator() config.add_route('test', '/test', my_view, renderer="templates/my_template.mako") config.add_route('test', '/test', my_view, renderer="json", accept="application/json") </code></pre> <p>If request comes with header <code>Accept</code> set to <code>application/json</code> value JSON will be returned, otherwise you got rendered template.</p> <p>Note, this will work only if you have predefined set of data formats in which you want to encode responses from your views, but it's the usual case. In case you need dynamical dispatching you can decorate your views with <code>decorate</code> argument of <code>add_route</code> which will choose the right renderer with your rules.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs there a better way to switch between HTML and JSON output in Pyramid?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTheron Luhn
    1. USandreypopp
    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. CO+1 I think this best reflects the "pyramid way" of doing things. It's flexible, decouples the views from the renderers making the views easier to unit test because instead of parsing an html doc you can just look for values in a dictionary.
      singulars
      1. PO
      1. USTom Willis
    2. COThis does seem like a neat way of doing it. How would I go about applying this method to my Handlers methods? I found, in the documentation, that you can decorate functions with `view_config` which will allow you to set the renderer but I couldn't see an equivalent for URL Dispatch.
      singulars
      1. PO
      1. USdave
    3. CODoesn't `add_handler` works like this? I've never worked with handlers, but documentation states, that "Any extra keyword arguments are passed along to add_route."
      singulars
      1. PO
      1. USandreypopp
 

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