#django

it's always morning, somewhere

[just... not here]

enough foreplay, quantik ... what's the question ? :)

I have a modelForm and there is some of the fields that are foreign keys to other models. I wanted to override the default widget (input text instead of select) so that the user can provide a new value for these keys

ok

When the form is saved, I need to have some logic in my view to check if the key provided already exists. If not, I create it, and if yes well, everything is fine.

well, the fields should do a lot of that for you anyway

In order to validate my user inputs, I created additional forms for each foreign keys.

however... get-or-create on keys? ouch

yeah...

That's bad ?

The usage is for a typeahead, does that make sense to you ?

Basically I want to populate it with the keys that already exists, but let the user add new ones.

quantik, https://docs.djangoproject.com/en/dev/ref/model...

ok that's cool.

It will shorten some of my code. I have a follow-up question however.

If i use get_or_create, it wont validate the inputs right?

Right.

quantik, You can do that after you run is_valid() on your form.

PKKid2: tsk tsk... giving out dev doc links...

Ok. I have another question then

well, I'm off to lunch...

FunkyBob, :P

What if my form does not validate, Is there a way to bind the errors for this particular form to the one of my modelForm ?

Basically if it fails, I dont want my form to display an error related to the fact that the foreign key is non existant, but insteand, have one saying why the foreign( which is a charField with custom validators) did not validate.

FunkyBob, thanks for your help, I got it figured out

quantik, i hate form handling in django.

i struggled a lot to have a intermediate save option on model forms into the database, and ofcourse managing predefined templates provided by django form/formset

quantik: You're completely in control of the validation messages.

ennajelari: Tools like crispy forms and formulation make rendering much more flexible.

ennajelari: you're under no obligation to use django Form's rendering ability...

The shortcut output (Just using {{ form }}) really isn't meant to be customized, it's just a quick, basic structure for convenience. If it doesn't work for you, you're much better off just rendering individual fields where you want them, or using a helper app.

mattmcc: aww.. thanks :)

mattmcc, let met check that :). but i had a issue today that, i could not control "This field required" into the place where i wanted into the template.

Placement, or the wording?

placement

hey funkybob i need help with some URL mapping

You just need to put {{ field.errors }} where you want it. (Or loop over it, since it's a list)

im getting this error

The current URL, rango/category//add_pages/, didn't match any of these.

webscrapper1: It's not lying. That path didn't match any of your urlpatterns.

i know

Try it without the double slash.

mattmc, true, that means to avoid default placement of errors, i need to iterate manually all the fields in the form to be displayed in the form. Once i do that, i get all the fields which i donot want to display also.

mattmcc: placement :)

heres my url path the problem is

urlpatterns = patterns('',

url(r'^$', views.index, name='index'),

url(r'^about', views.about, name='about'),

url(r'^category/(?P<category_name_url>\w+)/$', views.category, name='category'),

url(r'^add_category/$', views.add_category, name='add_category'),

url(r'^category/(?P<category_name_url>\w+)/add_pages/$', views.add_pages, name='add_pages'),)

ennajelari: Fields that you don't want to display should've been excluded in the first place.

webscrapper1: don't paste in here!

sorry

and the fields which i dont want, i kept in the hidden field, and then the field is not posted as part of the request.POST.

woops

ennajelari: Because just not displaying them doesn't prevent their values from being changed by the user. If they shouldn't be changed, they shouldn't be in the form.

the category_name_url

i dont know how to get that recognized

it works for the other page

where did the url come from? the one that's failing

mattmcc, what i am doing is i am creating the dynamic form in the UI through ajax, once you click add more button lets say, i create a backend model instance for the same.

webscrapper1, \w+ looks for at least one \w

Anyone know of a good django store/shop/ecommerce app/project? open source

man i cant believe how much easier writing an ORM Model is in django than in symfony

Nelluk: I came from PHP, I used the Kohana framework over symfony, I now hate PHP. lol :P

and keeping the primary key of newly created instance into the form, so that i can use it to update the fields provided by user which is invalid

umm im supposed to pass the category to the page views

Django + Python = Awesome. <3

so the url is in that structure

havent heard of kohana myself

moneydouble: try https://www.djangopackages.com/grids/g/ecommerce/

mattmcc, intention is to keep saving the form what the user enters, and once saved, then while user submits, i need to do validation.

So there was a mention here that QuerySet union with ManyToManyFields can produce a wrong count: http://stackoverflow.com/questions/4411049/how-...

ennajelari: Well, I don't know how much I can help with your particular use case, I was just pointing out that if you're avoiding iterating over the form's fields because it has things you don't want, you're doing what we call "fighting your tools"

im working on the exercises there

Anybody knows if this is a reported issue on the Trac?

Iterating over the fields is a really easy way to handle custom form rendering, it's not something you should want to avoid.

wow i only just encountered the way django templates fail to iterate on defaultdicts because lookup precedence. that was annoying.

I tried searching with the 'queryset union' keywords, but none of the results seem related.

mattmcc, getting the point :). Do you have any suggession to implement partial form saving?

But more importantly, having fields in your form that aren't displayed is not going to prevent their values from being changed by a user who knows the names of those fields.

k_sze[work]: The ORM can't do unions.

moneydouble: havent looked at ecommerce django packges til now. kinda want to play with one, thanks a lot ;)

Hipikat: explicitly call keys?

k_sze[work]: It can combine criteria, but that's not the same thing.

since our ecomm site is on.. umm. cough.. classic asp

Nelluk: haha, nice.

FunkyBob: did you make a store app? seems like I recall you saying you had one.

FunkyBob: keys unknown. just casting to dict() before passing to template… :)

moneydouble: am currently working on a rather large store...

mattmcc: 'combine criteria' as in combining the 'WHERE' clause?

k_sze[work]: Yeah.

FunkyBob: open-source?

nope

ah

I've done some simple stores at times...

oscar commerce looks pretty nice

mattmcc: then I wonder how that bug was at all possible in the first place.

k_sze[work]: Well, if the combined criteria results in different joins (e.g, outer joins instead of inner) than what you were expecting, it would effect the results.

does this seem like a sensible way to do postgres master / slave replication ? https://www.digitalocean.com/community/articles...

i'm looking to add some ansible plays that setup postgres master/slave repliction. I've never done it before though.

airtonix: how does it compare to what's in the actual Postgres docs?

Nelluk: oscar is very nice. very similar to django-shop but more sensible and mature

ive been playing with it and reading its docs for a few minutes. only negative i can see is that it has some dependencies that arent that actively developed, so who knows if it'll ever be py3 compatible

FunkyBob: I wouldn't know, since I've not read the postgres docs to find that. I don't imagine there would be some conten there that is along the lines of "Best practice setup of master / slave replication"

Nelluk: i doubt it will be for a while. but then isn't that true of most django apps?