Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You should use a custom Authorization class that blocks the list endpoints and gracefully raises an error instead of just removing the URL all together so it still plays nicely with Tastypie.</p> <pre><code>class UserObjectsOnlyAuthorization(Authorization): def read_list(self, object_list, bundle): raise Unauthorized("Sorry, no list reads.") def read_detail(self, object_list, bundle): # Is the requested object the user? return bundle.obj == bundle.request.user def create_list(self, object_list, bundle): raise Unauthorized("Sorry, no creates.") def create_detail(self, object_list, bundle): raise Unauthorized("Sorry, no creates.") def update_list(self, object_list, bundle): raise Unauthorized("Sorry, no updates.") def update_detail(self, object_list, bundle): raise Unauthorized("Sorry, no updates.") def delete_list(self, object_list, bundle): # Sorry user, no deletes for you! raise Unauthorized("Sorry, no deletes.") def delete_detail(self, object_list, bundle): raise Unauthorized("Sorry, no deletes.") </code></pre> <p>EDIT:</p> <p>If you'd like to force this API always to be a 'Detail' request then you can override Tastypie's built in functions. Basically if you specify an ID in the URL then tastypie routes it to be a _detail request and if you don't then it routes it to be a _list request. If you override the dispatch functions which detect this, you can change all requests to this resource to be _detail and specify what the primary key is to look up your user. This may be a bit more hacky, but will accomplish what you want:</p> <pre><code>def dispatch(self, request_type, request, **kwargs): # Force this to be a single User object return super(UserResource, self).dispatch('detail', request, **kwargs) def get_detail(self, request, **kwargs): # Place the authenticated user's id in the get detail request kwargs['id'] = request.user.pk return super(UserResource, self).get_detail(request, **kwargs) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PORemoving the list endpoint from a resource on tastypie
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRudy Mutter
    1. USRudy Mutter
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORemoving the list endpoint from a resource on tastypie
      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. VTAcceptedByOriginator
    1. COBut I still want the list endpoint url to behave as the detail endpoint: /api/v1/user must return a user. There is no need to specify the user id, since the api will always return the sabe object.
      singulars
      1. PO
      1. USMarcio Cruz
    2. COEdit added to my answer to address forcing this to be a 'detail' response instead of a 'list' even when not specifying a primary key for the resource.
      singulars
      1. PO
      1. USRudy Mutter
    3. COI have up on completely removing the list endpoint and did somwthing like you suggested: transforming the list endpoint into a detail endpoint. Not exactly what i wanted, but more simple and cleaner.
      singulars
      1. PO
      1. USMarcio Cruz
 

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