On 3/30/06, yml <[EMAIL PROTECTED]> wrote:
>
> Thank you you are amazing
>
> here it the solution
> =
> if new_data['localisation']:
> print "new_data contains : " +str(new_data)
> loc=new_data.getlist('localisation')
> print 'lo
Thank you you are amazing
here it the solution
=
if new_data['localisation']:
print "new_data contains : " +str(new_data)
loc=new_data.getlist('localisation')
print 'loc : '+str(loc)
print "new_data['localisation'] co
On 3/30/06, yml <[EMAIL PROTECTED]> wrote:
>
> This is an amazing tip. I didn't know that I could print messages in
> the runserver console.
> I was missing that a lot. this is eaxcltly were the problem is for some
> unknown reason the information is correct in new_data but when I am
> retrieving
This is an amazing tip. I didn't know that I could print messages in
the runserver console.
I was missing that a lot. this is eaxcltly were the problem is for some
unknown reason the information is correct in new_data but when I am
retrieving new_data['localisation'] I got only the last piece of t
On 3/30/06, yml <[EMAIL PROTECTED]> wrote:
>
> Your suggestion give the same result:
> temp.set_localisation(map(int,new_data['localisation']))
>
> Only the last selected localisation is saved.
>
>
I think you can print new_data['localisation'] to see if it's what you want.
--
I like python!
My
Your suggestion give the same result:
temp.set_localisation(map(int,new_data['localisation']))
Only the last selected localisation is saved.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To
I have added an additional temp.save.
First I create the Profile with the mandatory attributes then I add the
optional ones if they exist.
This seems to work, I mean I do not get an error message when clicking
on submit.
My problem is now that even if I multi select localisation I only save
the la
On 3/30/06, yml <[EMAIL PROTECTED]> wrote:
>
> I don't set any value for the profile_id. This attribute where added by
> django, I guess in order to have a "primary key".
> If I comment the line with set_localisation (which is my many to many
> relation) I do not get this error so I do not see why
I don't set any value for the profile_id. This attribute where added by
django, I guess in order to have a "primary key".
If I comment the line with set_localisation (which is my many to many
relation) I do not get this error so I do not see why I should care
about this with this additional attrib
On 3/30/06, yml <[EMAIL PROTECTED]> wrote:
>
> hello limodou,
>
> you have been of great help till now, thank you for your time.
>
> I tried list because I was not working without:
>
> temp.set_localisation(list(new_data['localisation']))
> =
> error page w
hello limodou,
you have been of great help till now, thank you for your time.
I tried list because I was not working without:
temp.set_localisation(list(new_data['localisation']))
=
error page with: list(new_data['localisation'])
On 3/30/06, yml <[EMAIL PROTECTED]> wrote:
>
> Hello djangonauts,
>
> I wrote my first manipulator and there is still some part that I am not
> understanding.
> I have the feeling that I am missing something obvious in the save
> function of my manipulator but I am unable to improve it.
>
> I woul
Hello djangonauts,
I wrote my first manipulator and there is still some part that I am not
understanding.
I have the feeling that I am missing something obvious in the save
function of my manipulator but I am unable to improve it.
I would be glad if someone could explain me how to set_localisati
13 matches
Mail list logo