Re: ManyToMany in a custom manipulator?

Hi again, I think I found the answer to my own question, here: http://code.djangoproject.com/wiki/ManipulatorScript I hope this is useful to someone. mikah -- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google

ManyToMany in a custom manipulator?

Hi, I'm writing a custom change manipulator for a model. I'm not using the default because there's some special processing that has to happen on each save. Now, this model has a ManyToMany relationship. How do I add a form field that will update that relationship? In effect, it has to work on

Re: MyFormWrapper.myfield works in {{}} but not {%%} ?

Thanks. I think I figured it out. It's not the expr tag, it's {%%}. It seems that {%%} doesn't cause a form field to render into HTML the way {{}} does. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django

Re: Context as Stack?

Hi Eugene, Thanks for this example. I think it'll be helpful for me. I'm working on something like this right now, where I need to generate a whole bunch of small and simple subtemplates inside of a main layout template. I was worried that I might have to write a custom tag -- I can, but it

Re: integrating complex SQL updates with manipulators?

Ivan Sagalaev wrote: > Is it necessery that moveNode is called before get_validation_errors? > If not, I think this should go into manipulator.save(). If yes, why? No it's not necessary ... I see, so I should override manipulator.save() then? Does this mean subclassing manipulator?

Re: integrating complex SQL updates with manipulators?

Hi, I'd like to clarify with some sample code. I hope this makes my question clearer. My question is about the line marked with an uppercase comment. Mikah # def modify(request, item_id): ''' View to modify a single node. ''' try: manipulator =

integrating complex SQL updates with manipulators?

Hi, I'm currently implementing a table of nested sets using Django, based on Joe Celko's discussion of the subject. For those of you not familiar with it, the only really relevant part of the problem is that when you modify certain database fields, the corresponding fields in some other

Re: adding stored procedures / postgres functions to db?

Hi Malcolm, Got it. That's all I need to know. Thanks! Mikah -- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To

Re: adding stored procedures / postgres functions to db?

Malcolm and Adrian, Thanks so much for your quick replies! I thought of that, but I didn't know if it was the Djangoic way of doing it. Follow up question -- are _all_ the files in the sql/ directory executed, or just those that have the same names as the models? mikah --

adding stored procedures / postgres functions to db?

Hi, I'm trying to implement a complicated sequence of updates inside a form-handling view, and I realized that it might be best to do it inside a Postgresql function. In fact, I've already found sample code for a postgres function that's almost exactly what I need. My question is, how do I

Re: Creating a menu structure

I'm going to try to do the same thing as well. I have a vague idea that I have to write a custom view for it, but I'm still trying to figure out the right way to do it. Any pointers? --~--~-~--~~~---~--~~ You received this message because you are subscribed to