Hey again,
sorry, I just found https://github.com/django/django/pull/11452 . So I
guess I'll wait for Django 3.1 in August 2020.
Best,
Johannes
On Sat, Oct 19, 2019 at 9:22 AM Johannes Wilm
wrote:
> Hey,
> I noticed that there is no news concerning a standard json field in the
> 3.0 release not
Hey,
I noticed that there is no news concerning a standard json field in the 3.0
release notes. What would the most future-proof way be of incorporating a
json field currently? Should one use django-jsonfallback and hope it will
eventually land in mainline django or is that just meant as a proof
Dan we don't need a user-operated flag, instead we would introspect the
database version in use and have a database backend feature. For example
here's where the MySQL backend determines if the "over" clause is supported
for window functions:
https://github.com/django/django/blob/master/django/db/b
I'm for this. My only advice is that only some versions of Oracle have a
native JSON type. The oracle backend should probably use some query to
determine whether the Oracle instance supports JSON field, or there could
be a flag in OPTIONS about tihs.
On Tuesday, February 19, 2019 at 7:44:40 A
Hello ,
I would like to work on this. I recently started working on django. I want
to participate in GSoC so this might work for me.
Would you mind helping me.
On Thursday, June 23, 2016 at 3:27:07 PM UTC+5:30, Raphael Hertzog wrote:
>
> Hello,
>
> in almost all projects I work on, I end up usi
Hi,
On Saturday, October 20, 2018 at 10:48:04 PM UTC+2, Adam Johnson wrote:
>
> The main thing is that MySQL added a binary JSON type, whilst MariaDB just
> made the JSON type an alias for TEXT (plus the corollaries that implies):
> https://mariadb.com/kb/en/library/json-data-type/
>
Yes, this
The main thing is that MySQL added a binary JSON type, whilst MariaDB just
made the JSON type an alias for TEXT (plus the corollaries that implies):
https://mariadb.com/kb/en/library/json-data-type/
On Sat, 20 Oct 2018 at 21:36, Tom Forbes wrote:
> Awesome work! Would you mind elaborating on the
Awesome work! Would you mind elaborating on the differences between mysql
and mariadb?
On Sat, 20 Oct 2018, 05:14 Raphael Michel, wrote:
> Hi everyone,
>
> I used the sprints at DjangoCon US to work on this issue in form of a
> third-party package. Mainly, I created a subclass of
> django.contri
Hi everyone,
I used the sprints at DjangoCon US to work on this issue in form of a
third-party package. Mainly, I created a subclass of
django.contrib.postgres.fields.JSONField that
- includes code from django-mysql to work on MySQL 5.7+ as well
- does some nasty hacks to even work on Mar
I would also be very interested in helping out. I don’t know if this is
useful, but I’ve had a brief look at the feature support compared to our
current baseline Postgres features:
MySQL: https://dev.mysql.com/doc/refman/8.0/en/json-search-functions.html -
JSON_CONTAINS_PATH() can implement most o
I'd be up for helping with a database-agnostic one. One thing to note about
MySQL world is that MariaDB diverges more from MySQL here and I haven't
found the time to fix the differences here in Django-MySQL's JSONField. I'd
get on with it if I knew someone needed the work for a DB-agnostic field
th
Sorry, what I meant was a Django field. (I wasn't clear enough.)
Charles Leifer has good posts covering SQLite+JSON http://charlesleifer.com/
His Peewee ORM has a
JSONField http://docs.peewee-orm.com/en/latest/peewee/sqlite_ext.html#sqlite-ext
I was just wondering if someone knew if someone had
> Anyone know of an SQLite implementation?
A quick search shows the JSON1 extensions exists:
https://www.sqlite.org/json1.html
According to the release history (https://sqlite.org/changes.html) this was
added in version 3.9.0 (2015-10-14).
But I have no direct experience working with it.
On Thu
This has come up again, with an example implementation for Oracle:
https://code.djangoproject.com/ticket/29821
Anyone know of an SQLite implementation?
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
T
So, I think a DEP is needed. I think we should start with the following for
every database supported by Django (and the more common 3rd party ones):
If every major DB supports JSON out of the box, we may I mean we just
forced everyone to go to Python3. We haven't hit an LTS since. Maybe
bumping u
Hey,
is anyone working on this? Have this patchwork of solutions for different
databases systems in additionally the uncertainty associated with not
knowing which of the postgresql solutions will survive in the long run
really makes it a difficult decision to switch to anyone of these from a
p
Yeah I got similar problems , I'm working with django 1.11 and rest
framework I wrote [1]
we got about 5 options for JSON Fields
https://pypi.python.org/pypi/django-jsonfield
https://pypi.python.org/pypi/jsonfield
from rest_framework.serializers import JSONField
from django.contrib.postgres.f
Current maintainer of https://github.com/bradjasper/django-jsonfield here
and I would definitely support this.
-Brad
On Thu, Jun 23, 2016 at 9:28 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Hello,
>
> On 23 Jun 2016, at 15:40, Tim Graham wrote:
> > Marc said, "I'm happy
On Friday 24 June 2016 14:49:54 Raphael Hertzog wrote:
>
> Did my answer clear your doubts?
>
It moves my opinion of the feature from -0.5 "are we sure we need this" to -0
"I won't stand in your way".
Shai.
I would like it. I honestly one use JsonField to store json data, not
really to query it, and having postgres store it a very efficient way is a
very nice plus compared to plain text storage. Then the postgres features
to query json data are godlike but I wouldn't mind trading something to
allo
Hi,
Le vendredi 24 juin 2016, Shai Berger a écrit :
> > 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
Le vendredi 24 juin 2016, Aymeric Augustin a écrit :
> On 24 Jun 2016, at 09:01, Raphael Hertzog wrote:
> > Why would you want to discourage people?
> Well, this seemed to be the latest decision, but I don’t care much myself.
AFAIK only Marc Tamlyn insisted on such a requirement to have native JS
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 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 t
On 24 Jun 2016, at 09:01, Raphael Hertzog wrote:
> Why would you want to discourage people?
Well, this seemed to be the latest decision, but I don’t care much myself.
> What would be the next logical step if I want to work on this?
>
> Is there a need for a DEP to discuss the interface provid
Hi,
Le jeudi 23 juin 2016, Aymeric Augustin a écrit :
> 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 so
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
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
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
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
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
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-
31 matches
Mail list logo
