Hello,
in almost all projects I work on, I end up using a JSONField. Since
I value being able to run with any database, I'm not relying on
django.contrib.postgres.fields.JSONField. So I have been using
pypi's django-jsonfield maintained by Matthew Schinckel:
https://bitbucket.org/schinckel/django-
I would also love to see this in Django. Although I mostly use Postgres, it
would be nice not to be locked into a single database vendor if I were to
use a JSONField.
On 23 Jun 2016 7:57 PM, "Raphael Hertzog" wrote:
> Hello,
>
> in almost all projects I work on, I end up using a JSONField. Since
On Thursday, June 23, 2016 at 12:12:51 AM UTC+2, Shai Berger wrote:
>
>
> Thanks for this thoughtful clarification. I think I understand your
> position
> much better now. If
Thanks for reading, Shai. I know my English is far from perfect, so I
appreciate your involvement.
I understand corr
Same boat for me.
I constantly need the JSON field but can't always rely on postgres.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send
1 up on this one, would be really useful for me as well!
On Thursday, 23 June 2016 10:57:07 UTC+1, Raphael Hertzog wrote:
>
> Hello,
>
> in almost all projects I work on, I end up using a JSONField. Since
> I value being able to run with any database, I'm not relying on
> django.contrib.postgre
Making JSONField a core field was discussed in
https://groups.google.com/d/topic/django-developers/sAgYOqBUvgI/discussion
Adam said, "my recent completion of its *JSONField* for MySQL 5.7+ is very
similar to the *contrib.postgres* one, copying and adapting large parts of
code from Marc Tamlyn's
Hi Marcin,
Thanks for taking the time to clarify constructively your use case.
On 23 Jun 2016, at 13:10, Marcin Nowak wrote:
> If it will not use migration files when they already exists, it sounds ok.
I believe that this point was a big misunderstanding in the discussion.
As far as I underst
Hello,
On 23 Jun 2016, at 15:40, Tim Graham 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
Has a feature like this ever been considered?
If a model has no __unicode__, __str__ or __repr__ representation, then
maybe it could devise a string representation by collecting fields which
have this value set to True.
Example:
Without the feature:
class Person(models.Model):
first_na
