DjangoBot: #django

yashh: how would I capture the sluggify?

jlilly u mean u want to populate the form with data or what?

neuro more info neeededd

yashh: well, I'd like to use a forms.ChoiceField that only shows a subset of the available data.

hmm

there's a property on the choicefield you can override to change its queryset

so if the form is about wanting to buy a Toyota, it shows the possible models of Toyota, not all of the models. [So not Models.objects.all() but Models.objects.filter(brand="Toyota")]

you'll want to subclass the form to accept a parameter, and then update the querysets in the constructor

hrm. alright, thx.

may be ajax stuff jlilly

yashh: well now I'm passing into a function the sluggified url that replaces what's in the models database with different caps and spaces

so I can search every entry and compare using the sluggified versions of both what's in the database and what I'm searching for

yashh: I don't think it should be, tbh. If you're already rendering an object, you should have relevant information to build the correct form sans ajax.

Just have to figure out how to do it :)

but trying to convert the sluggified URL back into a proper case etc...to search the database models could cause more problems.

the problem is with your design then

neuro

u are in deep trouble

oh yeah it's definitely in my design lol

see make ur database design like this

Title, slug

ok?

slug should be populated from title

url look up should be done through slug

there's no question of converting them in run time and them search

yashh: so have the model store it slugified then eh?

hrm...I like that idea.

ys

may be check out django blog design

Entry has a title , slug,

yashh: so it was just slugify('string')

hmm

yes

depends how to u add data

if it through admin add prepopulated_fields in admin.py

if it through any custom form modify ur save() method to add slug = slugify(title)

yashh: yeah...that's what I tried doing by overriding the models save method...but it's giving me errors saying asset_description a field is not defined.

thats a different attribute I think

yashh: so model form needs to be changed?

oh this is annoying I was so close to finishing buggar

looks like my sunday just got donzo

dpaste it

that's the error.

that's the model itself with the save() method overriden

ok

got it

its self.asset_description

oh whoops

my bad again, all the different languages I keep coding in I keep forgetting to do that...oop is a little different between python, java/c/c++

yashh: hey though seriously appreciate you walking me through my silly mistakes today :)

no problem

I am near exhaustion

its time to leave

and njoy a good movie

monday starts my routine

damn I love weekends

is there a way to define a class for the elements of a form in django.forms ?

yashh: heh, yeah dude I hate my job

yashh: and so monday - friday = hell :(

what do u do?

Under what circumstances could a QuerySet give me the same record more than once?

thats a pretty big violation of being a set.

It gives you rows that are in the DB

yashh: how do I get the urls.py to accept the sluggified url?

ironfroggy: did you set it to distinct?

So if there're duplicate rows in the DB, you'll get them

what would be the regex for the one word that contains '-' instead of spaces?

hey, are there any good signal docs out there?

that take into account the latest changes

neuro_damage: What do you mean "the one word"

Any word that contains - ?

im not talking about distinct values, im talking about the exact same record being in the set ELEVEN times.

my god neuro it catches the whole slug in one variabel

specifically changeset 8223?

keseph: well it's for instance ... ahv-iv-380-buggy-vibrator

may be u can seperate them in the view

that isnt what a _set_ is. a query from a relational database should never include a row more than once!

So, [-a-z0-9]

ironfroggy: False. False. False.

QuerySet is in no way related to formal sets

ok I am really exhausted

thats it for the day

well, it IS called a querySET, so i assume at least the most basic behavior of a set.

bye

And there is absolutely nothing inherent in RDB to prevent duplicate rows

(r'^models/(?P<model_to_search>)\w+', search_models),

No.

No. No. No.

anyone???

It's natural language

signals???

yashh: alright dude later

sure

So it's a convenient way to refer to a collection

u can catch me on twitter

And Set is a lot shorter to type than QueryCollection

i cant imagine any circumstances that would say "hey, whatever results this includes, give it to me like a million times because im a moron"