one more thing,
it is not incorrect to do something like
{
"\u0066\u006F\u006F":"\u0062\u0063\u0072"
}
instead of {"foo":"bar"}
it's an extreme example,
but it happens all the time in non-ASCII JSON.
I may prefer one over the other,
but really I don't care, and nor should I care,
because it would be wrong to assume a particular implementation.
in hindsight,
I think it was unfortunate that "some thing like a hash table" was mentioned,
in passing, when the object feature was explained in detail.
it gave the wrong signal that there was some kind of clever optimisation going
on,
but 4D will not talk about it in detail.
that was not the context.
it was simply a demo to show how using an object property name, which is case
sensitive,
is much faster than "Find in array". that was all.
it had nothing to do with QUERY BY ATTRIBUTE,
it had nothing to do with automatic indexes,
it definitely had nothing to do with optimising storage.
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
