Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Update</strong></p> <p>I've adapted the apply_filters method linked below to use the values before making the <code>distinct</code> call. </p> <pre><code>def apply_filters(self, request, applicable_filters): qs = self.get_object_list(request).filter(**applicable_filters) values = request.GET.get('values', '').split(',') if values: qs = qs.values(*values) distinct = request.GET.get('distinct', False) == 'True' if distinct: qs = qs.distinct() return qs </code></pre> <p><code>values</code> returns dictionaries instead of model objects, so I don't think you need to override <code>alter_list_data_to_serialize</code>. </p> <p><strong>Original response</strong></p> <p>There is a nice solution to the <code>distinct</code> part of the problem <a href="https://groups.google.com/forum/?fromgroups=#!topic/django-tastypie/YWyeYjmhqUQ" rel="nofollow">here</a> involving a light override of <code>apply_filters</code>.</p> <p>I'm surprised I'm not seeing a slick way to filter which fields are returned, but you could implement that by overriding <a href="http://django-tastypie.readthedocs.org/en/latest/resources.html#alter-list-data-to-serialize" rel="nofollow"><code>alter_list_data_to_serialize</code></a> and deleting unwanted fields off the objects just before serialization.</p> <pre><code>def alter_list_data_to_serialize(self, request, data): data = super(PersonResource, self).alter_list_data_to_serialize(request, data) fields = request.GET.get('fields', None) if fields is not None: fields = fields.split(',') # Data might be a bundle here. If so, operate on data.objects instead. data = [ dict((k,v) for k,v in d.items() if k in fields) for d in data ] return data </code></pre> <p>Combine those two to use something like <code>/api/v1/person/?distinct=True&amp;values=first_name</code> to get what you're after. That would work generally and would still work with additional filtering (<code>&amp;last_name=Jones</code>).</p>
    singulars
    1. This table or related slice is empty.
    1. POFilter on a distinct field with TastyPie
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdokkaebi
    1. USdokkaebi
    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
    1. COThis approach doesn't eliminate the duplicate names because the `distinct` operation happens first, so I get distinct `Person` objects not distinct `first_names`.
      singulars
      1. PO
      1. USkeathmilligan
 

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