#django

After processing my form in a view, what's the difference between rendering a Thank You page and using a HttpResponseRedirect?

redirect to a thankyou page?

I'd like to customize my thank you page with some details from what was submitted

If you don't do a redirect, the user may accidentally re-submit the form by reloading the page. https://en.wikipedia.org/wiki/Post/Redirect/Get

you can do that with a "rendered" one, but...

can I add contect to the redirect?

reisio: it's bad form?

you can use session variables, or query strings, or any number of things

s/contect/context/

so, best practices says the HttpResponseRedirect is the best choice?

If you're writing something to the DB, you could set a session variable with the object's PK.

either will suffice, so you may as well go with the path of least resistence

SteampunkDuck: code.djangoproject.org

mattmcc: Thanks for the wiki link, that's exactly what I needed!

hello everyone

'lo django091

sorry, .com

Koterpillar: I always want to type .org, too

it's registered but doesn't resolve, on purpose, I guess

Are there any simple security checkers for django?

what do you want to check?

think a large part of using django at all is that it has a lot of security builtin

Koterpillar: well I'm not exactly sure, anything, leaky cold

eg. is there anything like

chid: you can do something like manage.py check (and I think there are more *check), but really, read OWASP and think

Koterpillar: Hey, a few days ago I asked about is_popular. Remember?

well I'm reading OWASP but I'm really after automatic checking

no package will warn you that one of your views does an eval() on things, or you put {{ stuff | safe }} where you shouldn't have

MoZu4k_: I remember that you did

Koterpillar: it'll be nice if there was a package that listed them all out

well, pylint will do some things

Koterpillar: I went and studied up on db indexes; Now I’m unsure as to how having an index on the is_popular field which is just true or false allows for instant access from an index, since it will still have all the posts just sorted by is_popular

Koterpillar: am I still thinking about this incorrectly?

they are not just sorted by is_popular; there's a pointer to where the "true" starts

I've done this https://docs.djangoproject.com/en/1.8/releases/...

Koterpillar: Oh! Is there? Why is that the case?

Koterpillar: I thought each row in the index just had the pointers to the related row

MoZu4k_: ever seen an index in a paper book?

Koterpillar: Yes

it lists words for each letter

so you can quickly find the letter you need and then all the words that start with it

in your case, you will have two "letters": True and False

once you find "True", you'll be able to list all records that have is_popular=True

Koterpillar: How is this actually implemented? Does the index store those pointers in a bookkeeping block or something?

you can visualize it as {"a": [10, 12, 13], "b": [11, 14, 9]}

that's stored on disk, of course, not as a Python dictionary, and is much more complex, but the principle is the same

right, it’s a b-tree or something I think

thanks Koterpillar

look up "database index" or some DBMS courses for more details... these are heavily optimized, so there's a lot of techniques

oh, indexes are b-trees in postgres. cool

They might be.

Postgres supports several index types, optimized for different kinds of data.