QuerySet.select_for_update

In strict_fields mode, you can't pass an empty value back in a datetime field, even if the schema says it's nullable.

the save() method does this:

if hasattr(self, "id"):
    self._client(self.id).put(self._get_fields())  # return bool
else:
    self._setattrs(**self._client.post(self._get_fields()))

See: https://github.com/ikeikeikeike/tastypie-queryset-client/blob/master/queryset_client/client.py#L664

The problem is, that in the TastyPie docs, it says that a create will return a header that shows the new location of the created object. But the code here is expecting some content - there is always a zero response:

http://django-tastypie.readthedocs.org/en/v0.9.11/interacting.html#creating-a-new-resource-post

And slumber does not pass on the response headers, it just clobbers the whole thing and turns it into a string.

So - very likely this should not be expecting a response string at all.

QuerySet.distinct

QuerySet.bulk_create

override or config or patch.

QuerySet.values

QuerySet.defer

Similar to Django Paginator.

Release version 0.5.2.

× Multiple iteration.

paginator = Paginator(objects, 100)
for i in paginator.page(1):
    print i

○ Single iteration.

paginator = Paginator(objects, 100)
for i in paginator.page(1).object_list:
    print i

add auth.py to tests directory.

QuerySet.exclude

QuerySet.using

QuerySet.complex_filter

Add a Django Server for tox test.

QuerySet.only

Exchange to requests from the slumber.

• set_field
• get_field

QuerySet.in_bulk

QuerySet.reverse

QuerySet.aggregate

×

inbox_message = client.inbox_message()
inbox_message.message = message.resource_uri
inbox_message.inbox = inbox.resource_uri
inbox_message.save()

○

inbox_message = client.inbox_message()
inbox_message.message = message
inbox_message.inbox = inbox
inbox_message.save()

I have a related attribute on my objects that aren't named according to the related type.

So, suppose I had a BlogResource and a PostResource, my PostResource's name for its parent Blog wasn't simply "blog", but rather, say, "foo". This causes accesses to post.foo to fail due to _model_gen looking up the model_name (which is the attribute name) in the schema.

If this doesn't make sense, I can provide some sample code. I'm just knee deep in debugging something and wanted to make sure I made a note of this before I forgot.

QuerySet.extra

QuerySet.update

QuerySet.values_list

QuerySet.prefetch_related

QuerySet.dates

QuerySet.iterator

QuerySet.annotate

In code i have something like this:

api_priv = Client(settings.API, auth=(username, password))
api_pub = Client(settings.PUBLIC_API)

Both of those API have different models except class Client. With differs with fields and queryset. Both objects have same content in _schema_store field and if one of those load schema other does't do it.( because -> https://github.com/ikeikeikeike/tastypie-queryset-client/blob/master/queryset_client/client.py#L758). Call this code raise error:

api_priv.client.objects.first().private_field
api_pub.client.objects.first().public_field  #  <- raise exception "obj have no attribute public_field"

It's happens because while creating Client obj metaclass set _schema_store on static class field( code -> https://github.com/ikeikeikeike/tastypie-queryset-client/blob/master/queryset_client/client.py#L710)

Possible solution is change ClientMeta that way to create new SchemaStore when obj use different base_url parameter or store some how SchemaStore dict where key is base_url and value schema_store.