#django

hey funkybob can you break down twitter bootstrap into one sentence. What is it and whats its purpse?

making your frontend beautiful and easy

I have a very simple model, https://dpaste.de/kpf1 - when I do {{ user.user_questions_values }} I see the relationship manager… how can I get the value? There can be multiple records in UserQuestionsValues for this.

moneydouble: since user_questions_values can be many, you need a loop

{% for obj in user.user_questions.values.all %}

^

Oops, user_questions_values

exit

then inside the for loop you can do obj.value

ahh right, I forgot the .all part lol I knew I had it right

The models

Has anyone used this before? https://github.com/bread-and-pepper/django-userena

Thanks schinckel johnb25

no worries

whats the best way to capture the data from a submitted form and post it to database?

A ModelForm?

just build the form to pass it to the correct view

webscrapper1: I did mention you should go read the "Forms for models" docs

and then grab the form data from the request variable

well for the form to post the data the correct url, which is linked to the correct view, and then grab the request.POST['formid']

or whatever the syntax is

...Or use a ModelForm.

Or a generic view ?

johnb25, schinckel - maybe I'm still half asleep but I feel like I should know this… how would I get the question name? If I have this: {% for obj in user.user_questions_values.all %} how do I get the UserQuestions model.name? {% endfor %}

webscrapper1: use a ModelForm

{{ obj.userquestions.name }} doesn't work

ok

moneydouble: You named your FK 'question'

modelform seems like a lot of work if this is a one off

mattmcc: oh duh lol, I was trying to get another relationship vs the field.

Thanks

moneydouble: you should take a rest :)

hehe

ill be back tomrrow funkybob thanks for the guidance

Who's assuming it's a one-off? And assuming a model exists (Which is the typical way to put things in databases with Django) then a ModelForm would be less work than manually moving the data from request.POST to the model object for saving.

johnb25: lol yeah I didn't sleep last night and took a 30 min nap :P

hmm, true

that makes sense, i kind of glossed over the fact that it automatically saves the record

Strange. We are using a MySQL backend for one of our projects. Somehow some of the new tables get varchar fields created with the latin1_swedish_ci collation whereas all the old tables are in utf8_unicode_ci.

k_sze[work]: serves you right for using mysql :P

isn't the swedish collation default for mysql?

FunkyBob: legacy PHP app ported to Django.

we haven't had the time to move everything to PostgreSQL yet.

at least it's on the cards :)

(so I hope)

MySQL is horrible.

I had to help some colleages tune an app using it the other day

still

it's not only stupid and slow, but it also makes it hard to tune

the other newish tables created by Django are all utf8_unicode_ci. I don't know what happened to cause the latest ones to be created as latin1_swedish_ci.

Could be worse. They could be encoded as utf8_swedish_chef

bork! bork!

utf8_klingon_kli

Hi all. Trying to create a model with a django.contrib.gis.db PointField in a second database. The second database, "geo," is using django.contrib.gis.db.backends.postgis

… my default db uses django.db.backends.postgresql_psycog2. I have a router set up, but when I run ./manage.py sqlall geoapp I get "AttributeError: 'DatabaseOperations' object has no attribute 'geo_db_type'" — implying that sqall tried to use the default db instead of my specified db in the router. Very tough problem

Any thoughts? I'll post my router

Here is my router https://gist.github.com/anonymous/f716517e91657...

BTW I am running django 1.5.1

hejirarijeh: did you check the release notes for django 1.5.2 through 1.5.5 ?

No not yet, is there some stuff on this?

not sure... worth a look

So, btw, I am using the same syntax for the router regarding allow_syncdb as the 1.5 docs (https://docs.djangoproject.com/en/1.5/topics/db...). But yes, let me take a closer look at the release notes.

Just paged through the 1.5.2->1.5.5 release notes. No mention of routers or syncdb.

It just really seems to me there is something wrong either with my understanding of routers or the way that django is processing my router. I only have one router, and it seems to me that my logic enforces that syncdb cannot be called using the default db. My router is also in my settings.py file. If I place a "raise" in my router between lines 19 and 21, an error is never raised.

(if i put a raise between lines 21 and 23 an error is raised)

(raised when I call "/manage.py sqlall geoapp" as mentioned above)

Ok. So maybe the deal is I just need to run "./manage sqlall geoapp --database=geo" … this seems to work.. I guess that if not database is hinted, then default is used and allow_syncdb never results to geoapp

Okay, this makes sense… now to try to figure out how to get this to work with south

(WELL! Sort of makes sense. Not sure why django even gets to the error… it seems to me that app_label will always be geo app so returns false on allow_syncb.. weird)

Yup. South is broken on this. blargghhh. Oh, well.

Anyone know how I can go about getting a little more help with this router issue? I've run into something similar (with sqlite3—stuff ending up in the default db when it doesn't seem like it is the right place) with the router. I'm wondering if it even could be a bug, as unlikely as it may sound.