#django

anth0ny: there’s a group by in sql

delgiudices: have you googled it? this looks close: http://stackoverflow.com/questions/12731897/gro...

anth0ny: thanks yeah i just googled it

Katharsis: well, if it’s auto, it’s not editable. Nor is it nullable.

You’re telling it two different things. Or three.

Can I use an actual url in urls.py?

hi, if do something like a = Model.objects.all() and then a lot of a.filter(), will there be a seperate query for every filter, or will django do that from memory?

Boogymanx: what are you really trying to do?

Nimos: querysets are evaluated lazily

I'm trying to change my user management from what I wrote (which was pretty shitty) to the user management in a third-party app

ok, so do that. how does that relate to your question, though?

When I'm using my login, which currently is this: url(r'^login/', '/forum/user/login/', name='Login'), I get the error 'str' object is not callable

https://dpaste.de/30pY traceback

err, when I'm trying to log in* not using my login

show me the urls

Boogymanx: that can never have worked

the second argument to url() is invalid

Well, it doesn't

That's why i'm here :p

tbaxter: https://dpaste.de/auYi urls.py

either use 'myapp.view.login_view' as a fully dotted python path to your view (discouraged) or use the actual callable (i.e. from myapp.views import login_view and url(..., login_view, ..)

MarkusH: why is it discouraged? I remember when I first did the tutorial that's how urls were created, although that was still 1.6 or maybe 1.5

Boogymanx: we changed the recommendation to use strings in iirc 1.6

because you get better error messages when something fails

All right, thanks :)

i.e. the import error is thrown in the urls.py not somewhere in django.utils.importlib or wherever that was

Need help filtering a list of products using reverse foreign key field!? What am i doing wrong -> https://dpaste.de/0uoy

when I send a dictionary to render with a form object how do I call it from the template?

same as any context

This will sound weird: Is it possible to save a model to the DB without calling .save()? I am doing a bit data migration and need to insert models from one DB into another DB. A lot of models have special things that occur on save (such as emailing a user) and I don't want those to run

but paste some code

anth0ny: use sql instead of the ORM.

carljm: you’re a genius

carljm: yeah, the hard part is following all of the foreign keys, iterating the the django sets would be easier for me

tbaxter: I tried {{ careerform }} and {% careerform %} neither worked

my lack of sql-fu is holding me back from going raw dog sql

anth0ny: you probably don't need Django for this?

Walkman: yeah, I think you're probably correct.

anth0ny: well, it's ugly as sin, but if you really want to stay in Django-land you can probably do a nasty hack with super()

hydraidm801: i'm new at this, but i did something earlier today that sounded like what you want:

{% for type, count in sum.items %}

<th>{{ type }}</th><td>{{ count }}</td>

{% endfor %}

carljm: yeah, okay, sql it is

anth0ny: SQL isn't all that scary, just takes a bit of study if you're rusty :-)

oh nevermind I have my url as TemplateView.as_view derp

carljm: yeah, i was having fun with it when i was just duplicating DBs (which was totally doable in the beginning). Now I have sort these models and move them (and all the models referencing them) into a new DB and that's when i start getting dizzy

can a model have two fields that reference the same foreign key in another model? ie. createUser and modifyUser both relate to entries in the usergroup model?

ckpoint: sure, why not?

well, the good news is, becoming good friends with SQL (and your db server's capabilities generally) allows you to solve a whole range of problems in better ways than if you treat your SQL db as a dumb ORM data store

ckpoint: they're different columns in the DB

anth0ny: thats what I figured, just didn’t want to break anything :) thanks

ckpoint: Django will ask you to give them different related_name, though

carljm: while this isn't #postgresql, do you have any sql pro-tips to bestow re: following FK relations?

anth0ny: "following FK relations" is pretty vague - might be more helpful if you phrase your problem in SQL terms (i.e. what tables do you have, how are they related, and what data-copying logic do you need to implement)

carljm: where do I specify the related names at?

ckpoint: in the ForeignKey definition

create_user = ForeignKey(User, related_name='created_by')

carljm: found the docs thanks

or some such

actually that naming is all wrong, but whatever, you get the idea

haha

by default does FK allow null

no

k I’ll overide

carljm: okay, so I have a db that has a bunch of instances of a Camera model. I have a lookup table that stores CameraID and ClientID, telling you which camera belongs to which client. Images and Videos have a FK to the camera that took them. Cameras also have a FK to a Location. This goes on and on.

carljm: The goal is to iterate through all the Cameras, put every Camera, Image, Video, and Locaton into the proper Client DB. So, I need to follow those relations and insert them in an order that doesn't break dependencies. So, any help tips regarding that?

note: Camera Location doesn't change, if you're wondering why that relationship exists

I'm getting a "matching query does not exist" and (strangely) can prevent it by printing the instance in question. See http://pastebin.com/J1WJyZpt. Thoughts appreciated...

how do I eagerly load all fields of a given Model instance?