Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Encountered the same problem a few months back doing a single-page app that consumes a REST based api. What I came up with after searching for answers was to use HTTP's existing 401 and 403 error. I had my api return these errors. Then caught the exceptions by using an extended error handling model to handle these errors and just routed them to my login via the router <a href="http://backbonejs.org/#Router-navigate" rel="nofollow noreferrer">navigate</a> function. </p> <pre><code>var ErrorHandlerModel = Backbone.Model.extend({ initialize: function(attributes, options) { options || (options = {}); this.on("error", this.errorHandler); this.init &amp;&amp; this.init(attributes, options); }, errorHandler: function(model, error) { if (error.status == 401 || error.status == 403) { app.history.navigate('login', true); } } }); </code></pre> <p>In hindsight though i think it would have been better to just use a global jquery <a href="http://api.jquery.com/ajaxError/" rel="nofollow noreferrer">ajaxError</a> function instead. Snippet above was based on a similar <a href="https://stackoverflow.com/questions/6150514/global-error-handler-for-backbone-js-ajax-requests">question posted here</a> a few months back. </p> <p>I also had to override backbones default fetch behavior so i could trigger an error with the ogin to catch a response variable included in the json response of the api.</p> <pre><code>var Login = Backbone.Model.extend({ urlRoot: '/login', parse: function(resp,xhr) { if (resp.response == 'success') { app.history.navigate('dashboard', true); } else { this.trigger('loginError'); } return false; } }); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POWhat's the best design/architecture practice to manage authentication (session) & authorization in a backbone.js application
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USAnthony Chua
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat's the best design/architecture practice to manage authentication (session) & authorization in a backbone.js 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. 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. COThis sounds good. Where did you guys put in authentication check..was it in views or in controller e.g. lets say user lands on a dashboard after login now do you put in authentication code in controller instantiation or in view. I believe it makes sense to put in authorization check in views. Let me know if I am not clear enough.
      singulars
      1. PO
      1. USPradeep Kumar Mishra
    2. COIf by controller you mean the router, yes we're doing auth check on the router, as we have user roles. At the same time we're also doing auth check on views, for the same reason that we had to limit some events to certain user roles. For the actual user data we're actually using the Login model to store it and check this for the auth status. Just pasted a simplified version here.
      singulars
      1. PO
      1. USAnthony Chua
    3. COcool. Thanks a lot. Before closing it would you mind sharing some sample code.
      singulars
      1. PO
      1. USPradeep Kumar Mishra
 

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