#django

not liking this.... as i progress through the project, my models are ALL changing, from the initial design...its like the original design which took me ages...has ended up as just a guide, and every single model has changed.

possibly due to lack of initial understanding

i thought i was leading the project...but it now seems the project is leading me

Does the template {$ regroup %} only work on a list of dict objects?

I have 3 context variables that are QS. Is there a way to loop through them without passing them as one object in views?

I have a one-to-one field between a Model that I have called "Profile" and the User model (see https://dpaste.de/vCWt). When I try to change the number of points, it correctly changes, but doesn't save.

From my perspective, it seems like it might be because the two models are totally separate, and although they're connected through a one-to-one relationship, I'd have to save the Profile object to actually get the points to save (and not the model used in the form)

I forgot to include -- the model used in the form is this : https://dpaste.de/dSLj

And intuitively, it should really only be saving the TranslationRequest model, since that's the one in the form, but is there any way for me to also save the Profile model too? I don't really think I have any way to access it, although it's directly connected to the User model.

oh. nevermind, by explaining the problem clearly, I accidentally figured out the solution lol.

Quack

mattmcc: rubber ducky programming really is too effective :(

So effective it closed his page.

is datetime set at utc or local timezone by default?

AlwaysHigh: should be what's in your settings, in most contexts

hey i am using the __str__ method to return a name.

but i want the returned value to be a mixture of 2 fields eg return self.name appended to self.number

how do i do this

can i just use return('{}{}'.format(self.name, self.number)

in fact i should maybe just try it

Yep.

fantastic...this django is helping to solve a lot of problems

eb0t: could even use return f'{self.name}{self.number}' if your python is new enough :)

ah thanks...im on python 3.5 . i havent seen that method before

ah, they're new in 3.6

ok thanks, but it's even less code than the other method.. so it's a nice find.

hey do you guys think its a good idea to write company names to the database all in lowercase, regardless of how the user entered the name

just trying to work out if that is possibly a good move

eb0t: Probably not, business names may have specific capitalization, like using camel case (LinkedIn) that should be preserved.

ah ok ill stick with camel case .thanks mattmcc