Re: CrossDB JSONField — Testing needed.

The reason it behaves differently to jsonfield and jsonfield2 is that it does not use the built-in django.core.serializers.json.DjangoJSONEncoder. Therefore serializing Decimal fields fails. In my opinion the basic types, such as Decimal and Date/Time fields shall be serializable to JSON, but ap

Re: CrossDB JSONField — Testing needed.

Thanks for your testing! It's being passed through json.dumps to check it would be possible to store it as JSON. Seems legitimate to me. The other libraries default to an encoder that allows storage of Decimals, whilst the new field doesn't. Since Decimals don't round-trip in JSON (they're encode

Re: CrossDB JSONField — Testing needed.

Hi Carlton, hi Sage, I just tested this implementation against my JSONField form editor library, namely django-entangled , using SQLIte. As you can see from the testing matrix , everything works fine using

Re: CrossDB JSONField — Testing needed.

The error just reported, seems to be related to the use of Django's internal forms.DecimalField. If I change that to a FloatField, everything works as expected. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" gr

Re: CrossDB JSONField — Testing needed.

Hi Carlton, hi Sage, I just tested this implementation against my JSONField form editor library, namely django-entangled , using SQLIte. As you can see from the testing matrix , everything works fine using

CrossDB JSONField — Testing needed.

Hi all. >From GSoC last year, Sage has a CrossDB JSONField for us: https://github.com/django/django/pull/12392 We still have a bit more close review to do but... *We need people to give it an outing, to find issues/regressions and so on. * PostgreSQL: Clone your DB etc. Change your P