Deserialization issue

[boronine]

See 2e4bc5b for failing test.
See 1d4a029 for fix.

[boronine]

The fix is no good. Turns out the serialized value is a Python string (with unicode literals), not a JSON string. I'm gonna fix the test (to make it fail again).

[boronine]

Okay, now the value is serialized with JSON as well. Test passes.

[niwinz]

Hi!

Thanks for your efforts. But, your approach is wrong. Because:

• Hstore is not json and can not be treat as json (hstore alvays has string values and can not contains inner objects)
• This "strange behavior" on some environments not happens alvays. (I have some servers with it working fine)
• On my environment all tests pass ok and all works fine: ValueError: dictionary update sequence element #0 has length 1; 2 is required #11 (comment) Tests fail #12 (comment)

I need some test project for reproduce this strange behavior but this can not be fixed with this workaround.
This seems fixes this stranges behavior for some people but is not a good solution because a reasons that I explain before.

;)
Andrey

[boronine]

Hi Andrey,

1. Yes, Hstore is not JSON, but why can't it be treated as JSON? In order for Django fixtures to work the field needs to be serialized somehow. I think JSON is the best choice as it's supported by most languages and is secure (unlike eval or pickle, for example).
2. Looking back at the issue, I don't think it's going to get fixed by this pull request, however this pull request definitely fixes the lack of serialization support for djorm-ext-store. We need fixtures for our project so we're currently using my patched version.
3. I added a simple test for serialization support. It would be nice to test it more thoroughly, but I think this is better than nothing. Either way, the error is confusing, a NotImplementedError would be better than the current random exception (which happens, I think, from trying to iterate over a string as if it was a dict).

[niwinz]

I' am completely confused, sorry. I have been spoken about other issue.

Your are right. I would like some time for review it. But currently I have very litle time for it.
I try review it sooner as possible.

Sorry and thanks for your work.

[boronine]

No worries, and thanks for the project, we're finding it very useful :)

[niwinz]

Now merged with some fixes for python3.
A lot of thanks.