hash-map string keys are converted to symbols about monger HOT 3 CLOSED

Thank you for your speedy reply. It turns out to be somewhat painful to encode/decode a structure like:

{:_id 1 :content "blob of XML" :terms { "unigram" 1 "bi gram " 2 "a tri gram" 3 }}

... because 'keywordize' wants to convert all or none. I've fallen back to converting the string keys into composite keywords, a la { :bi_gram 2 }, which is fine for my use case.

That said, I do regard it as a bug that the default behavior of the library will silently change the layout of a hash-map of primitive structures on load/save. Looking at the code, it's not an easy thing to fix (you'd have to annotate the hash-map with metadata to know which keys should be keywordized, which is probably not worth it for such an uncommon case), but it might be wise to document this behavior prominently.

Thanks again!

from monger.

For functions where it matters there are extra parameters or options that control this behavior. The name is usually keywordize.

from monger.

Another option is to use monger.collection/find instead of monger.collection/find-maps and then use monger.conversion functions however you like, with keywordize set to true or not.

from monger.