#django

woops.... so instead of a field user_type, make a property user_type that returns "a if hasattr(self, 'userA') else b" or whatever

ok and i still want to create a OneToOne relationship with these 2 user profile models right? As in, each user profile model has a OneToOne with the base user model

yes

ok

will i need 2 different log in forms as well?

without that user_type field, how would the app know which userprofile model to use?

because it will have it or it wont

It's very much personal preference, but based on project requirements, of course. I prefer a single model with user_type field. Redundant data doesn't matter as much to me now as it once did - space is cheap.

You can make it work either way - and each has it's own complexities to work out.

thats probably the best answer at the end of the day ^

Lots of {% if <something> %} regardless of which path. :)

what do you need to add to a view function in order for reverse() to find it?

a name.

we got an easy way to do a GROUP_CONCAT in django (postgres) ?

morenoh149 https://docs.djangoproject.com/en/2.1/topics/ht...

morenoh149: you can't reverse a view function, technically, but a url pattern

covered in the tutorial too: https://docs.djangoproject.com/en/2.1/intro/tut... <-- on that page

who needs those, when they can waste our time ;)

Django has some incredible documentation, quite well organized, and very discoverable via search engine effort.

no mention of reverse on chap 3

if only it were heroin

It's worth it for any dev to spend an hour or two browsing through the different sections - clicking the next/prev links

strike that, even h you have to try once

morenoh149 apologies then. https://docs.djangoproject.com/en/2.1/intro/tut... equates to it on that page, as that template tag gets you a url by name

morenoh149 some further googling nets me this as well: https://docs.djangoproject.com/en/2.1/topics/ht... a good description.

chapter 3 in the tutorial does indeed explain that

I'm working backwards from the word reverse

it just doesn't mention `reverse()`, because let's be honest, who needs it

in any case I think my test runner is having issues finding the named route/view https://gist.github.com/morenoh149/948c8190d945...

I googled `django reverse url` for that last link I posted

morenoh149: while all the while you should be working forwards from "start here"

you'll either help or not, I have done the tutorial twice

i believe we did help before making fun of you ;)

morenoh149 do you namespace polls in your urls.py?

your top-level urls.py

hop: you make fun of everyone. its toxic

jaddison: yeah it's the namespacing I bet

i don't

thanks

next time, ask the real question

morenoh149 lots of people in here haven't done the tut, but still ask questions. Again, (my) apologies if I pointed you at a resource that didn't help because I assumed (it's the canadian in me)

you assumed on the information given, which wasn't nearly enough

I did indeed.

So, it's not namespacing? Hmmm, I can't think of anything else that would affect it, honestly.

hop I should have asked, rather than assumed, whether he'd done the tutorial. that blame lies with me!

also maybe she, not he

jaddison: you get some leeway for trying to help

but it's true, i'm too cranky. off to bed

Good riddance! :)

morenoh149 can you reverse any other of your url pattern names in your tests?

morenoh149 I wonder if (in your tests), you need to use the `urlconf` param for `reverse()`? see https://docs.djangoproject.com/en/2.1/ref/urlre...

morenoh149: did you paste your views and urls somewhere?

(also, the code that's calling reverse)

it's solved it was the app namespacing.

when you set a field name in a model to be a OneToOne to another model, what does it actually put in that field?

morenoh149 Glad you got it fixed.

firefox it's a 'restricted' foreignkey field.

Django itself manages the 'one to one' nature of it.

oic

morenoh149: oh great

why does admin.py need access to my custom user creation form?

nvm

is models.CharField(max_length=10, default='') best way to add nothing to the field when creating it?

hi again

with silly questin about rest framework

i have 2 models(User and Post)

i am using ListAPIView for User

but lets say, i want to use Post in the same template

i want to add some Posts to my context and use it in my template

firefox, for charfield - yes, you probably want blank=True too

how can i do that?

so i need to install django-sitemaps to use django.contrib.sitemaps?

with install i mean through pip

do*

no, it's django.contrib so it's part of django

ty :)

The context that is passed to template tags include "object". But it's a list named "dict" and is a bunch of dictionaries. Is there a reliable way to access "object"

Let me rephrase: "object" is in a dict that is part of a list

you mean you have context like context={'key': [{'object': object,}, {...}, {...},]} ?

I just set up a virtualenv in "~/../myproject" ... My question is, do I run "django-admin startproject myproject" from within this same directory or from within the next level "~/../myproject/myproject"?

i don't think you want 4 levels of myproject/ but it doesn't matter much

how do i set a field to some text in my model automatically with a form?

ok. I made a directory for myproject then ran "python3 -m venv myproject" ... should I have skipped the first step?

i dont have to actually use a hidden input do i?

I ran "python3 -m venv myproject" after cd myproject

I think I just answered my own question... since this is a virtualenv, I can make the env then make a directory within it for my project.

wait

you dont make your poroject directory IN the env

^ that

put it in the same directory as the env

and you don't want it in your version control, but it can be managed by excluding if needed

ok... so I just answered my own question wrong. Thanks

firefox, automatically with a form? like how?

you can override form save I guess, or which function saves the instance

as in form A will set user_type field to 'A', form B will set user_type field to 'B'

yeah, look up how form save it's instance .save() or .save_model() I'm not sure

so if i create my own def save, im overriding the default one?

ok