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

Re: CrossDB JSONField — Testing needed.

n JSON (they're encoded as strings and then decoded back as strings), I think the new JSONField is making the right choice here. On Thu, 6 Feb 2020 at 06:35, Jacob Rief wrote: > Hi Carlton, hi Sage, > I just tested this implementation against my JSONField form editor > library, nam

Re: CrossDB JSONField — Testing needed.

Hi Carlton, hi Sage, I just tested this implementation against my JSONField form editor library, namely django-entangled <https://github.com/jrief/django-entangled>, using SQLIte. As you can see from the testing matrix <https://travis-ci.org/jrief/django-entangled>, everything work

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 <https://github.com/jrief/django-entangled>, using SQLIte. As you can see from the testing matrix <https://travis-ci.org/jrief/django-entangled>, everything work

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 y

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

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

Re: Cross-DB JSONField ready for review

retain all the functionalities from the original JSONField to make migration less painful. Mariusz is going to prepare a review for the current implementation, so I think we'll be able to have a discussion about this as well. Regards, Sage On Friday, 13 September 2019 11:09:14 UTC+7,

Re: Cross-DB JSONField ready for review

Hi Ole, I'm interested in what you are trying to do with JSONExtract. I have a subclass of Func called JSONBExtractPathText that I use with great success to extract parts of a JSONB object. Also, as of Django 3.0, you can filter directly on an expression (that has an output_field of BooleanFie

Re: Cross-DB JSONField ready for review

e implementation of a cross-DB JSONField. > As someone who has been using the Postgres-specific JSONField extensively for dynamic, custom fields for the past couple of years, can I humbly suggest that the some more thought goes into the field lookup before the current approach is enshrined?

Re: Cross-DB JSONField ready for review

27;t say how excited >>>> I am about this feature. 💃) >>>> >>>> Kind Regards, >>>> >>>> Carlton >>>> >>>> >>>> On Friday, 2 August 2019 13:46:46 UTC+2, Sage M.A. wrote: >>>>> >>>

Re: Cross-DB JSONField ready for review

e: >>>> >>>> Hello, everyone. >>>> >>>> As a follow-up to this message >>>> <https://groups.google.com/forum/#!msg/django-developers/M4dYz7T2SUo/b5RVjJHxBQAJ> >>>> and this ticket <https://code.djangoproject.co

Re: Cross-DB JSONField ready for review

is message >>> <https://groups.google.com/forum/#!msg/django-developers/M4dYz7T2SUo/b5RVjJHxBQAJ> >>> and this ticket <https://code.djangoproject.com/ticket/12990>, I have >>> completed the implementation of a cross-DB JSONField. >>> I have submi

Re: Cross-DB JSONField ready for review

everyone. >> >> As a follow-up to this message >> <https://groups.google.com/forum/#!msg/django-developers/M4dYz7T2SUo/b5RVjJHxBQAJ> >> and this ticket <https://code.djangoproject.com/ticket/12990>, I have >> completed the implementation of a cross-DB JSONField

Re: Cross-DB JSONField ready for review

.google.com/forum/#!msg/django-developers/M4dYz7T2SUo/b5RVjJHxBQAJ> > and this ticket <https://code.djangoproject.com/ticket/12990>, I have > completed the implementation of a cross-DB JSONField. > I have submitted a PR <https://github.com/django/django/pull/11452>, >

Cross-DB JSONField ready for review

Hello, everyone. As a follow-up to this message <https://groups.google.com/forum/#!msg/django-developers/M4dYz7T2SUo/b5RVjJHxBQAJ> and this ticket <https://code.djangoproject.com/ticket/12990>, I have completed the implementation of a cross-DB JSONField. I have submitted

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

Hey Sage, Hey Parth. First-off welcome on board! 🙂 The goal for the next couple of weeks is to get more deeply involved, whilst I guess you start thinking about your projects too. You can follow here, the dashboard and the timeline

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

I had the same doubt in my mind, what is the best medium to contact mentors? -- 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 an email

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

Hello everyone, I would like to thank everyone in here and everyone involved in Django's GSoC participation. This project has been accepted and I will try my best to deliver. On a side note, do we have any communication channel other than this mailing list and IRC? I don't mind using them, but

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

Hi Asif, I don't mind at all, but I'm still a bit busy with college stuff now, so I'm not sure when I'll be able to do it. On Sunday, 21 April 2019 14:39:25 UTC+7, Asif Saif Uddin wrote: > > Hi Sage, > > Would you mind opening a draft proposal at django/dep repo? If you can > implement the POC

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

Hi Sage, Would you mind opening a draft proposal at django/dep repo? If you can implement the POC cross db JSON field, I as a maintainer of django-activity-stream would like to try this with that package. Looking forward to try your POC. Thanks, Asif On Tuesday, April 16, 2019 at 5:36:04 PM

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

Hi, Raphael. Ah, yes, I have seen your project, but I guess I forgot to link it in my proposal. It *is* very interesting, and I believe it will be helpful for anyone who wants to implement this. Let's hope we can make this happen. Thanks for the feedback! Regards, Sage On Tuesday, 16 April 2019

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

Hi Sage, Hi everyone, I lacked the time to read this mailing list in the past months, and someone at DjangoCon Europe just pointed me to this thread, so just for reference, I want to add some prior work that I did to the list: At DjangoCon US and thereafter, I developed a third-party implementati

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

ally. >>>>> >>>>> On Thursday, April 4, 2019 at 11:30:48 AM UTC+6, Sage M.A. wrote: >>>>>> >>>>>> Hi, Carlton. >>>>>> >>>>>> Thanks a lot for the feedback! >>>>>&

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

;>> suits with that, you might have some ideas of remaining issues analyzing >>>> the test failures initially. >>>> >>>> On Thursday, April 4, 2019 at 11:30:48 AM UTC+6, Sage M.A. wrote: >>>>> >>>>> Hi, Carlton. >>>&g

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

at 11:30:48 AM UTC+6, Sage M.A. wrote: >>>>> >>>>> Hi, Carlton. >>>>> >>>>> Thanks a lot for the feedback! >>>>> Ah, yes, looks like I missed that Oracle implementation. I've updated >>>>> my proposal accord

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

; Thanks a lot for the feedback! >>>> Ah, yes, looks like I missed that Oracle implementation. I've updated >>>> my proposal accordingly. >>>> To summarize: >>>> >>>>- Added info about Oracle implementation (see 1.1) >>&g

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

t for the feedback! >>> Ah, yes, looks like I missed that Oracle implementation. I've updated my >>> proposal accordingly. >>> To summarize: >>> >>>- Added info about Oracle implementation (see 1.1) >>>- Replaced 1 week of research

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

> >> Thanks a lot for the feedback! >> Ah, yes, looks like I missed that Oracle implementation. I've updated my >> proposal accordingly. >> To summarize: >> >>- Added info about Oracle implementation (see 1.1) >>- Replaced 1 week of research

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

d 1 week of research with 1 week of writing tests and docs >for POC SQLite JSONField (see 3.1.1 and 3.1.2) >- Replaced the idea of implementing HStoreField with writing >documentation for ArrayField, migration path, and SQLite+JSON1 (see 3.3.2) >- Took half a

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

POC SQLite JSONField (see 3.1.1 and 3.1.2) - Replaced the idea of implementing HStoreField with writing documentation for ArrayField, migration path, and SQLite+JSON1 (see 3.3.2) - Took half a week from the merging process into writing the aforementioned docs. - Wrote about the possib

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

Hi Sage. Thanks for the proposal. It's looking OK. Couple of points: - There IS an Oracle implementation. See the ticket here: https://code.djangoproject.com/ticket/29821 - Something that looks like an ArrayField, yes. HStore... not so sure it's worth mimicking. - On the time

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

Hi Sagar, That's cool! However, I am not quite sure what you meant. If you meant to ask questions on how to use Django, I think it's best to ask them in the django-users forum or the #django channel on IRC. I'm sure the community will be abl

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

same bro i am too, actually i have learned python in last semester and using djnago build a small project and trying to get more about django. if you dont mind can i ask question when i will stuck somewhere about django and you may ask to me if you will not getting we will try to understand what ma

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

Hi Sagar, I started using Django last year. I've been studying the codebase lately, and I'm still trying to understand the mixins and stuff for the database backends. I have submitted patches for two tickets (#30294 and #30295

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

by the way how much you know django On Tue, Apr 2, 2019 at 8:52 PM Sage M.A. wrote: > Thank you. > > On Tuesday, 2 April 2019 19:26:29 UTC+7, sagar ninave wrote: >> >> I appreciate Sage >> > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Cont

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

Thank you. On Tuesday, 2 April 2019 19:26:29 UTC+7, sagar ninave wrote: > > I appreciate Sage > -- 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 fro

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

Hi Michal, >From what I know, SQLite and MySQL have the json_array() function which can be used to store arrays. https://www.sqlite.org/json1.html#jarray https://dev.mysql.com/doc/refman/8.0/en/json-creation-functions.html#function_json-array Meanwhile, Oracle Database stores JSON as a VARCHAR wit

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Tue, Apr 02, 2019 at 04:41:36AM -0700, Sage M.A. wrote: > Hello, everyone! My name is Sage. I'm a 19-year-old computer science > student from Indonesia. I'm planning to join the Google Summer of Code > (GSoC) this year, and I want to contribute

Re: GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

I appreciate Sage -- 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 an email to django-developers+unsubscr...@googlegroups.com. To post

GSoC Proposal: Add Cross-DB JSONField, ArrayField, and HStoreField

Hello, everyone! My name is Sage. I'm a 19-year-old computer science student from Indonesia. I'm planning to join the Google Summer of Code (GSoC) this year, and I want to contribute to Django. I have written a draft for my proposal in this gist

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

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-jsonf

Re: Allow querying JSONField with F objects #29769

28 AM Mani S > > wrote: > >> Django's F objects does not perform JSON lookups. A ticket has been >> raised for the same https://code.djangoproject.com/ticket/29769 >> >> I have written a customer expression for querying JSONField and >

Re: Allow querying JSONField with F objects #29769

ritten a customer expression for querying JSONField and > * it works!* > > class KeyTextTransformFactory: > > def __init__(self, key_name): > self.key_name = key_name > > def __call__(self, *args, **kwargs): > return KeyTextTransform(self.key_name, *arg

Allow querying JSONField with F objects #29769

Django's F objects does not perform JSON lookups. A ticket has been raised for the same https://code.djangoproject.com/ticket/29769 I have written a customer expression for querying JSONField and * it works!* class KeyTextTransformFactory: def __init__(self, key

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

wrote: 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 wo

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

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 so

Re: Adding a database-agnostic JSONField into Django

> 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

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

with a basic solution between themselves with a > simple fallback to TextField whenever one is using a different database? > > On Monday, June 27, 2016 at 12:29:30 PM UTC+2, Brad Jasper wrote: >> >> Current maintainer of https://github.com/bradjasper/django-jsonfield >

Re: Adding a database-agnostic JSONField into Django

Monday, June 27, 2016 at 12:29:30 PM UTC+2, Brad Jasper wrote: > > 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@polytechni

Update specific keys within nested Django JSONField data

Hello ! I have come up with a solution to #29112 , using jsonb_set function. However, this function is only available from PostgreSQL 9.5, and we need to give support for PostgreSQL 9.4 as well. We can use PL/Python extension to write a custom funct

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

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: > >

Re: Adding a database-agnostic JSONField into Django

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.

Re: Adding a database-agnostic JSONField into Django

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 somethi

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

have native JSON support on all main databases. While this is nice and should be encouraged, it's also the kind of requirement which discourages people from working on it. We have working codebase(s) for a generic JSONField. I would like to pick one, clean it up, strip it down and make it

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

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 or

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into Django

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&#

Re: Adding a database-agnostic JSONField into Django

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

Re: Adding a database-agnostic JSONField into 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

Adding a database-agnostic JSONField into Django

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/schinc

Re: Extending JSONField serialization

> > > > It's not resolved - the ticket is open, and Accepted. > > Thanks. I've seen comment with status set to closed and I didn't notice the current. My fault. Marcin -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django it

Re: Extending JSONField serialization

On Wed, Jun 22, 2016, Marcin Nowak wrote: >On Tuesday, January 5, 2016 at 5:29:14 PM UTC+1, Tim Graham wrote: >> >> This came up in a ticket a couple days ago: >> https://code.djangoproject.com/ticket/25995 >May I ask why this ticket was resolved just by adding some information to >the documen

Re: Extending JSONField serialization

not understand why some 3rd party package has some significance here. Let's add encoder_class as an optional kwarg of JSONField and pass it to loads/dumps calls. Bad idea? Marcin -- You received this message because you are subscribed to the Google Groups "Django developers (Contribu

[Off topic] Re: Extending JSONField serialization

Pet peeve: Please ignore if you don't care about database technologies. On Wednesday 06 January 2016 17:12:34 Dwight Gunning wrote: > design models that are a hybrid of our traditional, schema-oriented > approach, but also include a JSON Field and offer the benefits of the more > recent schemaless

Re: Extending JSONField serialization

s only helpful if the user is able to customize both encoding and decoding of its messages. For instance, on one of our projects, we use a custom serializer that encodes complex types as {"__type__": "foo", "value": "bar"} dicts. Our deserializer can the

Re: Extending JSONField serialization

Aymeric, thanks for clarifying. I take your point for joins although I'm a bit surprised you don't feel JSONFields are appropriate for filtering. I haven't tried yet but I am interested in the ability to efficiently index into the JSONField (thanks to use of Postgres' jsonb

Re: Extending JSONField serialization

On Wed, Jan 6, 2016 at 9:58 AM, Tom Christie wrote: > Customizing the encoder (or even using DjangoJSONEncoder by default) isn't > so bad. > > I'm less convinced about the usefulness of customizing the decoder - once > you've encoded the data into JSON any additional type information is lost, > s

Re: Extending JSONField serialization

Customizing the encoder (or even using DjangoJSONEncoder by default) isn't so bad. I'm less convinced about the usefulness of customizing the decoder - once you've encoded the data into JSON any additional type information is lost, so casting back to python primitives is always going to need to

Re: Extending JSONField serialization

Hello Dwight, I was trying to express the fact that JSONField is appropriate for storing data that won’t be used for joining other tables, filtering, aggregating, etc. but rather just for reading. “Not mission-critical” was a simplification. That said, data that meets the criteria above tends

Re: Extending JSONField serialization

, at 18:37, Tom Christie > wrote: > > > >> Should JSONField accept additional kwargs to customize the encoder and > the decoder? > > > > Quick take here: > > > > That sounds like a bit too much "cleverness" to me. The most obvious > issue

Re: Extending JSONField serialization

It should be configurable and I like the kwargs idea. I've also had to monkey patch JSONField in this way for datetimes. Regards, Michael Manfre On Tue, Jan 5, 2016 at 12:48 PM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > > On 5 janv. 2016, at 18:37, To

Re: Extending JSONField serialization

> On 5 janv. 2016, at 18:37, Tom Christie wrote: > >> Should JSONField accept additional kwargs to customize the encoder and the >> decoder? > > Quick take here: > > That sounds like a bit too much "cleverness" to me. The most obvious issue > it

Extending JSONField serialization

> Should JSONField accept additional kwargs to customize the encoder and the > decoder? Quick take here: That sounds like a bit too much "cleverness" to me. The most obvious issue it'd cause is putting values of one type into the field, but getting objects of a dif

Re: Extending JSONField serialization

This came up in a ticket a couple days ago: https://code.djangoproject.com/ticket/25995 On Tuesday, January 5, 2016 at 11:18:01 AM UTC-5, Aymeric Augustin wrote: > > Hello, > > I’m using the JSONField provided by django.contrib.postgres for logging > arbitrary data to PostgreSQL

Extending JSONField serialization

Hello, I’m using the JSONField provided by django.contrib.postgres for logging arbitrary data to PostgreSQL. For this use case, I’d like my data to be JSON serialized with as little fuss as possible. Unfortunately lots of things (dates, datetimes, decimals, etc.) aren’t natively JSON

Re: Django 1.9 - JSONField

On Thursday 09 July 2015 00:18:09 Christopher Allan Webber wrote: > [...] It would > be nice to get this included into Django itself, and have it noted as a > Postgres-only feature. Then if other databases can eventually catch up, > include them alongside it. > I have to repeat Marc's implied qu

Re: Django 1.9 - JSONField

зователь lza...@ucs.br >> написал: >>> >>> >>> Hi all, >>> >>> I'd like to know why this feature will be only available on postgres and >>> not as a Field for any database, like this product? This Field would be >>> very use

Re: Django 1.9 - JSONField

nd >> not as a Field for any database, like this product? This Field would be >> very usefull for many users I think. >> >> https://github.com/bradjasper/django-jsonfield >> >> >> https://docs.djangoproject.com/en/dev/releases/1.9/#django-contrib-po

Re: Django 1.9 - JSONField

product? This Field would be > very usefull for many users I think. > > https://github.com/bradjasper/django-jsonfield > > https://docs.djangoproject.com/en/dev/releases/1.9/#django-contrib-postgres > > By. > -- You received this message because you are subscribed to the

Re: Django 1.9 - JSONField

son should not be used. There are many suitable third party apps which do a simple dumps/loads around a text blob. There isn't really any benefit in adding this to core in my opinion. On 7 July 2015 at 15:38, Michael Manfre wrote: > The django-contrib-postgres JSONField takes advanta

Re: Django 1.9 - JSONField

The django-contrib-postgres JSONField takes advantage of JSON being a native type that allows it's data fields to be used by the ORM, instead of just a text field that wraps json.dumps() and json.loads(). All of the core supported backends seem to have some flavor of native JSON support (MS S

Django 1.9 - JSONField

Hi all, I'd like to know why this feature will be only available on postgres and not as a Field for any database, like this product? This Field would be very usefull for many users I think. https://github.com/bradjasper/django-jsonfield https://docs.djangoproject.com/en/dev/release

Re: JsonField

i'm reading other post on this forum django use pickle to store non relational data with session... -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe

Re: JsonField

it was just an idea, Russel... maybe too hard to accomplish in the right way. i can use json field in my trunk and that's good for me. i thought maybe, with validators, django could be be able to accomplish some of the features of a non relational data store, without messing up with low lowel dat

Re: JsonField

django could archive to manage non-relational data on relational db. i don't want to use a non relational db, because i need foreign key and i need non relational data. read the couchdb guide, i think that you can find inspiration to create powerful things. i think that some ability of non relati

  1   2   >