Thanks, i've workaround this with empty string.
I was surprised when saw raw_post_data which looks very similar to GET
string. I confused this behaviour with JSON parser.
On 6 июн, 12:50, Jani Tiainen <rede...@gmail.com> wrote:
> On Sun, 2011-06-05 at 22:36 -0700, Constantine wrote:
> > Hi, a have a problem, but may be this is expected behaviour:
>
> > on client side i'm post:
> > $.post("my url",{myvar:null}...)
>
> > but on server side:
> > request.POST becomes {myvar:u'null'}
>
> > null deserialized to string. So, do i need to report a bug in tracker?
>
> It's not "deserialized" thus not a but but works as designed. HTTP
> POST/GET parameters are only strings. Nothing more, nothing less. Django
> doesn't do any magic by default.
>
> You can use some known notation to handle your data, like JSON which can
> serialize and deserialize data correctly.
>
> --
>
> Jani Tiainen
--
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 unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
