DjangoBot: #django

bigmamamonk: that's pretty vague

binjured: if you pass it to the template explicitly or use the context processor w/ requestcontext

oh well... I just need somebody experienced to recommend a reliable provider :)

:D

rozwell: hmmm, i'm trying to fix a caching issue where a view is cached so the value of a field will be X for all users, even when it should only be that for one user.

binjured: so don't cache the template if it depends upon the user

rozwell: will using a no_cache template tag override the cache of the view? it would have to be done on every page, effectively nullifying the cache entirely

no

there is no way to exclude a page from the cache middleware

bigmamamonk: i think i would ask elsewhere

k cheers anyways :)

bigmamamonk: it's not really a django-related question :)

Magus-: so, if i have a search box on every page that i want to populate with a user's most recently search when they are on the actual search page, there's no way i can do that while retaining a cache of the pages?

At the template level, you can cache parts of a page.

binjured: there's the template fragment caching tag

But naturally you can't cache a whole page, and then say "but change this one part"

mattmcc: but i could take the base template, wrap everything but the search box in a template cache, and do it that way?

ermmm... but that would probably result in every page having the same block content regardless of the actual page... ugh

i asked this earlier, but had to go before i got an answer: is there a way with the new admin to set the value of fields from a model that's being edited inline? it was possible with the old admin, but now doesn't seem to be working. the obvious method would be to add '?inlinemodel-0-fieldname=value' to the URL, which works fine for non-inline models (just '?fieldname=value'), but isn't working for inline ones

i guess my only real option is disabling the site-wide cache and implementing fragment caching throughout

binjured: if you're using the global cache middleware for everything, no, you can't make a part or entire page not cached

binjured: or you could look into a caching proxy

rozwell: right. i think i may be confusing myself a bit here, though... say i got rid of site-wide caching and i have a base template with blocks like "content", if i wrap that content block in a template cache, will that mean that regardless of what URL is gone to (since it is a base template extended throughout) that every page will display the cached version of the last page put in there?

binjured: presumably

is there anything like request.user.message_set for anonymous users?

rozwell: but i could wrap the contents of the child template in a template cache instead? or would that achieve the same result?

anyone have any ideas on my question, http://groups.google.com/group/django-users/bro...

binjured: i don't know exactly how it plays out

tehone: I don't have any solutions, but I tried almost exactly the same thing and couldn't get it to show up in the admin.

bummer

it seems simple enough

i guess it may take some kind of customized form or something then

rozwell: okay, so i might have thought i solution, but here's the question: does the never_cache decorator for a view have any affect on the site-wide cache? i.e., can i not cache views or is it simply all-or-nothing?

binjured: I clearly answered that before

you can not exempt a view from site-wide caching

at all

ever

clear enough this time? :þ

Magus-: indeed it is ;)

binjured: never_cache is for setting the never cache header on the response, for hinting to clients/proxies/etc. to not cache

Magus-: so basically the choices are all-or-nothing site-wide cache or template caches which cache a piece of the response regardless of which page is actually requested? i.e., /categories/one and /categories/two will be the same thing if the template is wrapped in a cache tag?

binjured: there's also per-view caching

binjured: but template seems to be what you want

rozwell: right, but would that cause the same problem as the /categories/ issue i mentioned above?

binjured: either that or do the caching in front of django

but you could cache every view except that one binjured

then use fragment caching on that one

problem solved

without fragment caching /everywhere/

although IME fragment caching is quite nice

Magus-: okay, that's what i was wondering... if it would cache the view regardless of the values passed to it (i.e. category_view(request,cat=1) and category_view(request,cat=2) would actually end up being the same thing if view-cached)

because it's just the one view that i don't need cached, assuming it doesn't do that

but i haven't slept in a long time and am probably over-thinking this a lot

binjured: i would assume the decorator is smart enough to not return the same response for all arguments passed to a view

rozwell: me too, but i hate making assumptions ;)

rozwell: but you're right to assume it, since the all-site cache is smart enough to not do it

binjured: it's not difficult to accomplish ;)

rozwell: but since it's caching final pages... bah. i will just try it. if the production site turns into the same 3 pages i'll know

I've got a bunch of junk permissions in the database. Am I liable to mess other things up if I delete them? What's the best method for removing them?

Well, if they're not referenced by anything..

p--, Kurushiyama: updated models for the ticket system, adds comments, etc

quantumsummers, nice

got any views done? ;)

not for popular consulption today, lol...sorry. we're gonna fix that up tomorrow

p--:

^^

geez

quantumsummers, cool.. let me know.. I've been to busy with other things to even start on that.. so I am hoping you get it semi done before I have the time to consider building one ;)

p--: ok we should be moving right along there, I know Kurushiyama has a nice one coming too

p--: you a fan of steppenwolf?

born 2 b wild ;)

quantumsummers, meh.. not really ;)

inagaddadavida baby!

is there some way i can linkify a foreign key displayed in the admin console?

so clicking it lets you edit the model it represents

all i have to do to delete django is rm it from the site-packages dir?

That rather depends on how it got installed in the first place.

i did a check out

a reminder on template syntax - I can't perform an {% ifequal foo|filter bar|filter %} and have it process the filters before the comparison, correct?

using svn

EyePulp hm, no?

can a block have the same name as a variable in a template?

Killarny I don't see why not

EyePulp I've never tried that combination specifically, but I've always been able to use filters in tag parameters, as far as I recall.

Killarny: as the two are completely unrelated, yes

hrm.

m1ke yep, just delete the directory

rozwell: in case you're interested, Place.objects.extra(where=['not exists (select 1 from app_restaurant where app_restaurant.place_ptr_id = id)'])

does what i need :-)

Hi, can someone help me with this? Im just new to django and im doing the tutorial on the 0.96 release. Everything is fine until i reach the admin part, it seems my browser doesnt show the javascript, i tried with safari and its the same, im usin OS X 10.5

_carson_: you're using the "./manage.py runserver" ?

FunkyBob: yes

is it a known bug that urlconf entries with capturing regex break matching with the url tag?

you mean urls with nested parens?

a simple capture does not break anything

or do you mean non-capturing?

a non-capturing named url matches properly, but a capturing url in the same urlconf is not matching, raises NoReverseMatch

Magus-, I would need an advice from an experianced Django coder like you - I'm rewriting ( basicly ) django-openid, and I have a small design decision to make, OpenID allows additional extensions, python-openid supports 3 of them, currently only 1 is implemented and is activate thru an additional agrument to the view

Killarny: try providing more info then :)