DjangoBot: #django

hense: the horrors of democracy

fualo: a forloop would handle that exception for you correctly

hense: I'm not using an iterator at all - the exception is from manager.py

hense: normally by whatever management position is responsible (i.e. top down)

models.Event.objects.extra(select={'relevance': match_expr}, where=[match_expr], params=[query, query])

it's within django

fualo: doesn't change my answer.

the code: http://dpaste.com/67254/

fualo: [where_expr] ? is that right?

subsume: where?

err

match_expr

where are you getting this code from?

should be right... is there a way to see the query extra created?

subsume: its a heavily changed version of this http://www.mercurytide.co.uk/news/article/djang...

oh lord. that thing.

which doesn't work

haven't seen that in like a year.

yea.

it's bad.

terriblebad

hopefully I can produce a better version, which can be shared

fualo: throw it on the stack there next to the 1000 other fulltext search apps

Can I use generic views to abstract RSS feeds? Like, if I want to have 10 feeds that are very similar, I don't have to write 10 different classes for each one, right?

rozwell: :-)

rozwell: well maybe you can suggest a favorite?

asorbus, yes, you're right

just write generic RSS Feed class ;-)

hi.. is there a way to make Django force a www. subdomain?

sayane_: all right, cool, so I'll just read up on generic views :) thanks

asorbus: are you not using the syndication contrib app?

chrishartim, there are many ways to do it. Best is to write custom middleware

rozwell: I haven't really done any research yet, just wanted to see if it was possible before I started reading a bunch of stuff

either way, Im still curious why manager.py is throwing a stopiteration exception

rozwell: so I'm not sure what you mean

asorbus: http://docs.djangoproject.com/en/dev/ref/contri...

asorbus, there is a framework for rss feeds

and atom ;p

chrishartim: http://docs.djangoproject.com/en/dev/ref/settin...

yeah, i'm reading that, but it seems like it wants a different class for every feed

or maybe I just haven't read enough of it

asorbus: you can subclass

rozwell: I'm not sure what you mean by that, sorry :(

asorbus: so you end up with several class definitions which are around 2 lines long. it's not really a problem

asorbus: well continue reading and then ask pointed questions if you have any

rozwell: okay, but then the URLconf will be really cluttered with stuff, won't it?

asorbus: no, not necessarily

asorbus: I think the feed docs detail how to make more complex feeds to avoid that issue

rozwell: if I subclass, won't the feed_dict need to have a key-value pair for every subclass?

asorbus: like i said, continue reading, play with it, then if you still have questions ask them here

EyePulp: rozwell: cool, I'll continue reading

so there is no way to see what SQL objects.extra turns out?

fualo: yes there's a way to see it

fualo: there's the method described in the faq as well as QuerySet.query.as_sql

didn't see that on the QuerySet API reference in docs, I'll check those places

fualo: it's not documented

fualo: it's part of the internals you shouldn't be messing with unless you know what you're doing

fualo: anyway, look at the FAQ

howdy

o/

hey, has anybody ever used random.sample on a queryset before?

rather, a large queryset?

curious if it makes the pony cry

idangazit: i'm not sure why you would

I guess I could do order_by('?')[:5} or whatever

yeah feeling stupid at 2:30 am

nevermind

rozwell: thanks

Is there a common cause of off-by-one errors in get_FOO_type() methods?

Sorry, get_FOO_display() methods

I'm using the object_list generic view, and it works fine if queryset is Model.objects.all(), but I don't get the object_list at all if I use Model.objects.order_by('column'). Is there a nuance here I'm missing?

Model.objects.all().order_by('column') ?

Model.objects.order_by(...) is fine

and equivalent to Model.objects.all().order_by(...)

holdenweb: pastebin your models

holdenweb: rozwell: nah, doesn't work either way. PostgreSQL shows that the query's getting run with either all() or order_by

OK ...