StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11606910
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-23T05:28:10.867
FavoriteCount
0
LastActivityDate
2012-07-23T05:28:10.867
LastEditDate
LastEditorUserId
0
OwnerUserId
743530
ParentId
11604045
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
There are a couple of issues with your code above. First, yes you can expose any custom manager to anything, regardless if you are using it tastypie or not. AdvertManager you defined above can be accessed through Advert.objects only if you have replaced it default manager with your own version. Second, the way you want to expose tastypie filtering on AdvertResource is orthogonal on how filtering actually works. All filters are applied as practically ORM filters in the form <code><field_name>__<filter_name>=<value_or_values></code>. Since in your example you are using <code>box=<number>,<number>,...,<number></code> tastypie explodes that into <code>box__exact=...</code> and tries to find <code>box</code> field in AdvertResource and fails as expected. If your advert has a field called <code>location</code> you could add <code>withinbox</code> as a filter for that field and filter by: <code>location__withinbox=<values></code>. If you want to keep your original approach, you would have to parse the box filter yourself from request.GET dictionary and then pass them to your own overridden version of <code>obj_get</code> and <code>obj_get_list</code> in AdvertResource. Finally, when extending <code>build_filters</code> you are only making a mapping between Tastypie filter and an ORM filter. In your example you are returning objects as a filter; instead simply define it as: <pre><code>{ 'withinbox' : 'point__within' } </code></pre> and convert the list of values into <code>Polygon</code> within <code>apply_filters</code> before it is handed off to the actual filter method.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPython TastyPie - Custom manager methods as filters?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USastevanovic
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPython TastyPie - Custom manager methods as filters?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.