#django

I'm trying to allow a user to upload a 'profile_pic' when they first create their account. What's the best way to go about this using DRF? Here is what I have: https://dpaste.de/9kTq

But it won't allow user to upload image during create(), only for a PUT request

chris0101 if you're trying to stay RESTful, maybe you should add an endpoint for profile pics

Koterpillar: I inspected the queryset. If I used an intermediate queryset, there is different SQL produced.

If I split that filter(), using an intermediate queryset introduces a LEFT OUTER join which is wrong.

chris0101: did you get my point?

can i prevent model.related_set.all() from generating a join?

without explicitly using RelatedSet.objects.filter(id=model.id) ?

@odarbelaeze: creating it's own model, and then setting up a relationship to user?

wait, my bad. it already does not generate a join. ignore question!

Does makemigrations/migrate automatically add all the models from models.py? Or did I forget something and that's the reason why I get a "no such table" error?

chris0101: yes, the API doesn't need to ressemble de database exactly, but that's an approach you can make

i have a boolean model field that I'm using a RadioButton yes/no widget https://github.com/codeforamerica/primerpeso2/b...

(admin.site.register() Perhaps?)

vmonteco: yes, it does, inspect the migrations to find out what happened

but for some reason its not requiring the user to pick one, any ideas how i can make it required in the form? it is in the model

vmonteco: admin has nothing to do with it

chris0101: furthermore, if the user does not upload a picture, then falling back to gravatar in the front-end is always a nice touch

glassresistor: the field has to have blank=False

Koterpillar: Hmm I see no migrations. I tried with no databases ( I erased the previous one)

@odarbelaeze: Ok. I'll try this approach. Thanks.

vmonteco: then did you run makemigrations?

Koterpillar: the model does

Koterpillar: Yes : "No changes detected"

chris0101: you can also return the gravatar url in case of a ProfilePicture instance not existing for an user

vmonteco: shouldn't really happen, are you sure your models are in an installed app?

Koterpillar: You may be right. I don't know why, but the 'main' app wasn't in INSTALLED_APPS anymore.

glassresistor: what's the field?

Koterpillar: Byt When I try to add it again, I got a ImproprerlyConfigured exception : "Application labels aren't unique, duplicates : main"

vmonteco: what's your INSTALLED_APPS?

Koterpillar: http://dpaste.com/29SBVGX If nothing is in it twice, shouldn't is be OK?

vmonteco: does main.apps.MainConfig say its name is 'main'?

vmonteco: and is it really the same as 'main' below?

Koterpillar: name = 'main' Yes! And in INSTALLED_APPS, this is 'main' as well if this is what you're asking.

vmonteco: figure out which config you want then, and leave only one. Also, try 'makemigrations main'

Koterpillar: Would replacing name = 'main' with name = 'mainconfig' be something ok?

vmonteco: why do you want to do that? If it's the same app, why do you want it twice?

https://docs.djangoproject.com/en/1.9/topics/lo... says this - 'console, a StreamHandler, which will print any DEBUG (or higher) message to stderr. This handler uses the simple output format.'

Shouldn't it be INFO?

Koterpillar: My coworked added this. I never used AppConfig before with previous versions of Django. :S

vmonteco: read the documentation first

Koterpillar: I guess you're right. :/ Thank you for the link!