PUT against non-existant url creates object at different url

[markotibold]

I only recently understood that it is allowed to use PUT to create a resource. It might be worth mentioning in the docs that this behaviour is supported by the framework.

Secondly, it doesn't yet fully work as it should. If you put against a url that does not yet exist, an object is created for you, but on a different one. I used the rest_framework_tutorial and it just created a new object with a pk that was the latest +1, which makes sense.

I than tried using slugs as primary keys, but haven't managed to get that working.

[tomchristie]

The intention is the the .pre_save() method should correctly set the pk or slug field, which I believed was working, but will take a look. I think there should be a test for it, but perhaps I missed it out, again will take a look...

[tomchristie]

generics.test_put_to_deleted_instance is the relevant test. Would be trivial to duplicate to test_put_as_create

On 28 Oct 2012, at 15:34, Marko Tibold notifications@github.com wrote:

I only recently understood that it is allowed to use PUT to create a resource. It might be worth mentioning in the docs that this behaviour is supported by the framework.

Secondly, it doesn't yet fully work as it should. If you put against a url that does not yet exist, an object is created for you, but on a different one. I used the rest_framework_tutorial and it just created a new object with a pk that was the latest +1, which makes sense.

I than tried using slugs as primary keys, but haven't managed to get that working.

—
Reply to this email directly or view it on GitHub.

[markotibold]

Will do sir.
On Oct 28, 2012, at 6:18 PM, Tom Christie notifications@github.com wrote:

test_put_as_create