#django

lordofthekebabs: i've done them before and they definitely help starting, but in general I find picking a project and making yourself do it is probably the best way...i tend to lose motivation with online courses

fission6: might need to do 2 step migration...making the field, copying values over and then removing the original

fission6: which isn't exactly seamless, but its very doable

Kangremu alright last question i know im taking a lot of your time :) do you tend to jump from project to project or do you usually obsses over one project and make it really good

So I have a queryset that is a few .union()s that each contain a few annotations. I'd like to pull a value from that QS to use in an exclude filter, but I'm getting "subquery has too many columns" as an error, regardless of what I pass to .values_list

Kangermu looks like i could directly migrate!

any ideas?

i definitely obsess over one...I'd rather have one really nice project on my github that I can show than have 15 half done projects

Kangremu alright it seems like im doing every step wrong aahahha, bt thank you very much tho

fission6: haha...nice....i didn't think you'd be able to for some reason (even though theres no real reason they can't just stringify the int)

can you link your github

which is what I assume it does

i would love to check it ouy

lordofthekebabs: haha...i've long since deleted my public stuff, sorry :P

whaat

but stuff like todo apps are easy enough

well i have already cloned twitter

and it works actually good

just want to advance myself

thanks a lot for tthe advices

not a problem

fission6: which django version are you running?

1.11.12

Has anyone experienced issue with DRF API Permissions? I am having issues because I want to compose my permissions, e.g. IsAuthor, IsAdmin, and if either passes they have access to the view, but DRF makes it so if any permission fails they are unauthorized

because of this I have to keep re-writing the same permissions logic over and over again

I have a few other roles, so for instance: IsAuthor or IsManager or IsStaff or IsAdmin and the permissions on an endpoint might be any combination of the above

hey guys. I have a model with a foreign key field. I want the user of the API, when creating, to supply the model without that foreignkey field. when creating a new instance for that field should be created.

and then I have issues when I want to do things like, only the Author/Admin can put/patch, (has_object_permissions method) but I want Managers/Staff to be able to retrieve it

omarramo make the FK nullable if you want to create the model without it

if you are using `drf` you can override the view method's `perform_create` to tack on the FK on save, or you could do it in the serializer, or you could override the model's save method

Ryanar, I did it in the serializer but it somehow doesnt apply for the fixtures

for the fixture models its still null

and in the admin interface that field is still required somehow

well your fixtures aren't using your Serializer

so of course that doesnt work

fixtures are kinda terrible

ah I see

better to use FactoryBoy / Faker libs to generate factories to produce model instances with fake data

unless you are talking about pytest fixtures?

and about the admin interface thing? how can I get the form where I have to select an instance of the referenced object to disappear?

Im using the normal fixtures but thats not a big problem. ill just assign it when I need it for now

the admin interface pulls automatically from your model, so if it is required in the admin, it is required on the model

you need to have `user = models.ForeignKey('User', null=True)`

if you want to be able to create the model without a FK reference

weird

Ah, no matter what I do can't figure out how to remove BLANK_CHOICE_DASH from ordering select within django-filter…

if you have that and it is still showing, you are overriding or supplying a custom form to the Admin site model that is requiring the field

not really weird, without that `null=True` you are saying this model has a foreign key constraint on another model that is not nullable, so it must always have that relationship

null=True makes it nullable in the db, blank=True makes it not required in modelforms/admin

true, I forgot about that! thanks knbk

when I create a model from the admin interface, the modelserializer's create() method will be called, right?

no, the admin uses ModelForms, it doesn't use your serializer

you are confusing django with django-rest-framework

ah ok

yeah Im just hacking things together right now, I have no idea about any of this

but its going ok so far

serializers are an abstraction introduce by django-rest-framework to deal with serializing/unserializing django models

and used by its APIView, and generic views/viewsets

you should be making a model form if you want a custom form for your django admin

where does this normally go? as in which file

and I use django-easy-select2 to quickly bake in searchable foreign keys

`<project>/<appname>/forms.py`

so if you have an app called `polls` it would be `polls/forms.py`

Django should make a `forms.py` if you use it's start app functionality

Ryanar, I defined a modelform with less fields, how do I apply that to the admin interface?

add a class variable `form = MyForm`

class PollAdmin(admin.ModelAdmin):

form = MyPollForm

now it somehow cant find my model

i am importing models and in the modelform it says model = models.MyModel

IDE autocompletes it and everything

error message says apps.app.models has no attribute 'MyModel'

would need to see the code

I'm getting a CSRF error when trying to go to the admin, can someone help me debug it?

lacrymology: depends, if that is all the information you have to offer, then no :þ

I'm making a deploy, it works fine in dev, but it's not working in deploy (i've got dev->deploy->stage->prod

apollo13: I don't know what else can help

I.. think I don't see the cookie being sent

lacrymology: well for starters, which error do you get?

on the POST

CSRF missing

is the CSRF token there in your browser?

if not you aren't including it

might be the middleware isn't being added in production

lacrymology: the exact error please

Ryanar: The cookie is being set on the GET, but the post doesn't seem to be sending it back, AFAICS

apollo13: CSRF verification failed. Request aborted.