Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would say that it's hard to solve this in a clean manner using express-resource, since it doesn't allow for route-specific middleware (at least not in a clean way).</p> <p>I would opt for a similar layout as an express-resource module, but route it with plain old express. Something like this:</p> <pre><code>// Resource var forum = { index: // ... show: // ... create: // ... update: // ... destroy: // ... }; // Middleware var requireRole = function(role) { return function(req, res, next) { if('user' in req.session &amp;&amp; req.session.user.role === role) next(); else res.send(403); } }; // Routing app.get('/forums', forum.index); app.get('/forums/:id', forum.show); app.post('/forums', requireRole('moderator'), forum.create); // Only moderators can create forums app.delete('/forums/:id', requireRole('admin'), forum.destroy); // Only admins can delete forums </code></pre> <p><strong>UPDATE:</strong> There have been ongoing discussions regarding route-specific middleware in express-resource, e.g. <a href="https://github.com/visionmedia/express-resource/pull/45">here</a>. The prevailing view seems to be to have an array per action, e.g.:</p> <pre><code>var forums = { index: [ requireRole('foo'), function(req, res, next) { ... } ] }; </code></pre> <p>You could take a look through the pull requests and see if there is anything you could use. I totally understand it, of course, if you don't feel comfortable with that. I'm pretty sure we will see something like this in express-resource in the future.</p> <p>The only other solution I can think of is along the lines of Jan Jongboom's answer, which would be to mount the resources with express-resource, but have middleware attached "outside" of that, something like:</p> <pre><code>app.delete('*', requireRole('admin')); // Only admins are allowed to delete anything app.put('/forums/*', requireRole('moderator')); // Only moderators are allowed to update forums </code></pre> <p>But I regret that this leaks URLs all over the place.</p>
    singulars
    1. This table or related slice is empty.
    1. POGroup/rule-based authorization approach in node.js and express.js
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USLinus Gustav Larsson Thiel
    1. USLinus Gustav Larsson Thiel
    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. VTBountyClose
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe problem is that there are a fair amount of resources and it's quite clean with express-resource. I am thinking about a small module which I can use with app.use(), but I don't know how to write this.
      singulars
      1. PO
      1. USPatrick
    2. COPatrick, I totally agree. See my update above for more discussion. There are more pull requests than the one I refer to regarding this. I'm not sure about it, but I have the feeling that TJ will work more on express-resource, express-namespace & co after 3.0 is out the door, seems to be quite a few changes.
      singulars
      1. PO
      1. USLinus Gustav Larsson Thiel
 

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