On Friday 24 June 2016 10:01:36 Raphael Hertzog wrote: > Hi, > > Le jeudi 23 juin 2016, Aymeric Augustin a écrit : > > On 23 Jun 2016, at 15:40, Tim Graham <timogra...@gmail.com> wrote: > > > Marc said, "I'm happy for JSONField to be made a core field on the > > > condition that it's underlying support is more than a text blob on all > > > our main databases. It sounds like this will soon be the case.” > > > > In order to discourage people from using JSONField on databases where it > > cannot be implemented efficiently i.e. not with a text blob, the best > > solution may be to add it to Django and raise a warning when it’s > > misused. > > Why would you want to discourage people? In the recent thread "Extending > JSONField serialization", you said yourself that the use-case for a > JSONField is clearly to store and retrieve data and not to make queries on > it with smart lookups. >
So, what you're suggesting is actually a thin wrapper around TextField, which deals with the JSON encoding? > Is there a need for a DEP to discuss the interface provided by this field? I'm not sure the scope justifies a DEP, but some discussion of the API should happen. Personally, I'm not yet convinced that -- assuming indeed we are talking about a thinly-wrapped TextField -- such a field needs to have a canonical implementation (one declared so by the Django project). Shai.
