Re: QueryDict and its .dict() method - why does it do that?

On 2015-03-28, at 11:37 , Stephen J. Butler <stephen.butler@gmail.com> wrote:
>
> Let's be accurate here: what PHP, Rails, jQuery, et al. do is not
> "non-standard". There's nothing wrong with their key-value pairs in
> the query string.

Well there is the problem that it's really not specified (so hardly a
standard), the original behaviour is very strongly linked to PHP's
interpretation of "arrays" as a mix of array and hash table
(foo[]=1&foo[a]=1; does Rails always output Hash objects with a mix of
string and integer keys?) and it actually loses information
(foo=1&foo[]=1) (which is compounded by PHP's other "innovations" in
handling query strings, I don't know if Rails or jQuery have seen fit to
reproduce the one where space and dots in keys are replaced by
underscores)

> Perhaps it would be better to think about this issue as Plain Standard
> and Enhanced Standard.

"Enhanced" would mean it's strictly better which is not really the case.

If you want a "better standard", just use a JSON query string. That'll
work everywhere, and you'll get to pass numbers and booleans through
unmolested.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/53DBA3D2-A8D2-4B9E-B3A2-ABD9605B5306%40masklinn.net.
For more options, visit https://groups.google.com/d/optout.