Re: Cross-DB JSONField ready for review

[Sage M.A.]

Hi Ole and Matt,

Sorry for getting back so late. I agree that having such a function would 
be very useful. I believe it can be done with most of the current 
implementation because I actually needed to compile the JSON path string 
from the KeyTransforms (except for PostgreSQL that uses a different syntax 
of its own). So, maybe I just need to add a check if it's an instance of 
JSONExtract and adapt accordingly.

However, I'm not really sure about killing the other lookups. I agree that 
it interferes with the possibility of using the lookup names as keys, but I 
was trying to 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, schinckel wrote:
>
> 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 BooleanField).
>
> Thus, you could write your first example as:
>
> MyModel.objects.filter(JSONBExtractPathText('field', Value('Foo the 
> bar?'), output_field=models.BooleanField())
>
> I think you could possibly do the other stuff using either an 
> ExpressionWrapper, or at worst a Case(When()).
>
> (I hang out on #django on IRC if you want to discuss this in a more 
> interactive manner).
>
> Matt.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/d3199e1e-97ed-4196-a94a-809e0eb063b0%40googlegroups.com.

Re: Cross-DB JSONField ready for review

[Sage M.A.]

Adam, that's what I thought at first. However, I don't know which section 
it should go under. Writing it on Model fields docs doesn't seem right. 
Maybe in a howto?

On Saturday, 3 August 2019 01:23:25 UTC+7, Adam Johnson wrote:
>
> Sage, I think that should go in the main docs, in the docs/ folder in the 
> repo, no?
>
> On Fri, 2 Aug 2019 at 18:09, Sage M.A. > 
> wrote:
>
>> Hi Carlton,
>>
>> Thanks! I hope it can be merged soon :D
>>
>> Oh, and by the way, where should I write a setup guide for SQLite+JSON1? 
>> I don't know where and how to put it in the docs. By linking to a page in 
>> Django wiki, perhaps?
>>
>>
>> Regards,
>> Sage
>>
>> On Friday, 2 August 2019 22:08:17 UTC+7, Carlton Gibson wrote:
>>>
>>> Hey Sage, 
>>>
>>> Super stuff! Well done on your effort so far. (I can'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:
>>>>
>>>> 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 a PR <https://github.com/django/django/pull/11452>, 
>>>> ready for review. Some folks have reviewed the PR multiple times 
>>>> (thanks!), 
>>>> but I think some more passes from new perspectives would be cool.
>>>>
>>>> Regards,
>>>> 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-d...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/38824b73-162f-49b1-8709-887cace1af7c%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-developers/38824b73-162f-49b1-8709-887cace1af7c%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
> Adam
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/bc75684b-dae2-4acb-bd4a-e24e5f9845b9%40googlegroups.com.

Re: Cross-DB JSONField ready for review

[Sage M.A.]

Hi Carlton,

Thanks! I hope it can be merged soon :D

Oh, and by the way, where should I write a setup guide for SQLite+JSON1? I 
don't know where and how to put it in the docs. By linking to a page in 
Django wiki, perhaps?


Regards,
Sage

On Friday, 2 August 2019 22:08:17 UTC+7, Carlton Gibson wrote:
>
> Hey Sage, 
>
> Super stuff! Well done on your effort so far. (I can'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:
>>
>> 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 a PR <https://github.com/django/django/pull/11452>, 
>> ready for review. Some folks have reviewed the PR multiple times (thanks!), 
>> but I think some more passes from new perspectives would be cool.
>>
>> Regards,
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/38824b73-162f-49b1-8709-887cace1af7c%40googlegroups.com.

Cross-DB JSONField ready for review

[Sage M.A.]

Hello, everyone.

As a follow-up to this message 

 and this ticket , I have 
completed the implementation of a cross-DB JSONField.
I have submitted a PR , ready 
for review. Some folks have reviewed the PR multiple times (thanks!), but I 
think some more passes from new perspectives would be cool.

Regards,
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/d68c0bb6-40cc-418e-b511-60caf4b5a8ca%40googlegroups.com.

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

[Sage M.A.]

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 I guess a faster and 
easier-to-access channel would be very helpful in the development of this 
project. I lost context every time I disconnect from IRC, so it's not very 
desirable.

Or, is django-core-mentorship 
<https://groups.google.com/forum/#!forum/django-core-mentorship> more 
appropriate? There hasn't been much going on there, so I'm not really sure.

On Monday, 22 April 2019 00:05:27 UTC+7, Sage M.A. wrote:
>
> 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 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 UTC+6, Sage M.A. wrote:
>>>
>>> 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 16:44:18 UTC+7, Raphael Michel wrote:
>>>>
>>>> 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 
>>>> implementation that does a little more than the ones that are more 
>>>> well-known and mentioned in the proposal: 
>>>>
>>>> https://github.com/raphaelm/django-jsonfallback 
>>>>
>>>> django-jsonfallback supports native JSON fields on PostgreSQL, MariaDB 
>>>> *and* MySQL (which are quite different in that regard). On all other 
>>>> databases, it falls back to the behaviour of just storing strings in 
>>>> text fields. Therefore, it's still different from what is being 
>>>> proposed here, and also the implementation is quite unclean in the 
>>>> sense that it needs to check for database backends on the level of 
>>>> database fields. When implemented in core, this could be done much more 
>>>> nicely. 
>>>>
>>>> Still, it might be an interesting thing to look at when doing this, if 
>>>> only for the test cases and the weird MySQL/MariaDB things. I'd love to 
>>>> see this in core and are happy to help wherever I can with my 
>>>> expertise. 
>>>>
>>>> Best 
>>>> Raphael 
>>>>
>>>> Am Tue, 2 Apr 2019 04:41:36 -0700 (PDT) 
>>>> schrieb "Sage M.A." : 
>>>>
>>>> > 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 
>>>> > <https://gist.github.com/laymonage/b53a1acbbab36b6cd526b48fd2a5>. 
>>>>
>>>> > I have submitted two small patches for Django, and I hope to 
>>>> > contribute more in the future. Feedbacks are much appreciated, 
>>>> thanks! 
>>>> > 
>>>>
>>>>

-- 
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 to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/56d64b7b-d803-4260-81f8-33959f3aa263%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sage M.A.]

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 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 UTC+6, Sage M.A. wrote:
>>
>> 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 16:44:18 UTC+7, Raphael Michel wrote:
>>>
>>> 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 
>>> implementation that does a little more than the ones that are more 
>>> well-known and mentioned in the proposal: 
>>>
>>> https://github.com/raphaelm/django-jsonfallback 
>>>
>>> django-jsonfallback supports native JSON fields on PostgreSQL, MariaDB 
>>> *and* MySQL (which are quite different in that regard). On all other 
>>> databases, it falls back to the behaviour of just storing strings in 
>>> text fields. Therefore, it's still different from what is being 
>>> proposed here, and also the implementation is quite unclean in the 
>>> sense that it needs to check for database backends on the level of 
>>> database fields. When implemented in core, this could be done much more 
>>> nicely. 
>>>
>>> Still, it might be an interesting thing to look at when doing this, if 
>>> only for the test cases and the weird MySQL/MariaDB things. I'd love to 
>>> see this in core and are happy to help wherever I can with my expertise. 
>>>
>>> Best 
>>> Raphael 
>>>
>>> Am Tue, 2 Apr 2019 04:41:36 -0700 (PDT) 
>>> schrieb "Sage M.A." : 
>>>
>>> > 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 
>>> > <https://gist.github.com/laymonage/b53a1acbbab36b6cd526b48fd2a5>. 
>>> > I have submitted two small patches for Django, and I hope to 
>>> > contribute more in the future. Feedbacks are much appreciated, thanks! 
>>> > 
>>>
>>>

-- 
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 to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/84045d73-2a55-4355-b939-e6e2a2b215f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sage M.A.]

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 16:44:18 UTC+7, Raphael Michel wrote:
>
> 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 
> implementation that does a little more than the ones that are more 
> well-known and mentioned in the proposal: 
>
> https://github.com/raphaelm/django-jsonfallback 
>
> django-jsonfallback supports native JSON fields on PostgreSQL, MariaDB 
> *and* MySQL (which are quite different in that regard). On all other 
> databases, it falls back to the behaviour of just storing strings in 
> text fields. Therefore, it's still different from what is being 
> proposed here, and also the implementation is quite unclean in the 
> sense that it needs to check for database backends on the level of 
> database fields. When implemented in core, this could be done much more 
> nicely. 
>
> Still, it might be an interesting thing to look at when doing this, if 
> only for the test cases and the weird MySQL/MariaDB things. I'd love to 
> see this in core and are happy to help wherever I can with my expertise. 
>
> Best 
> Raphael 
>
> Am Tue, 2 Apr 2019 04:41:36 -0700 (PDT) 
> schrieb "Sage M.A." >: 
>
> > 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 
> > <https://gist.github.com/laymonage/b53a1acbbab36b6cd526b48fd2a5>. 
> > I have submitted two small patches for Django, and I hope to 
> > contribute more in the future. Feedbacks are much appreciated, thanks! 
> > 
>
>

-- 
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 to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/588ca222-8d7f-4c34-8c4e-cffde8f35b57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sage M.A.]

I see, thanks for the info! Why is the ticket still open, though? Also, I 
still found one failing window test case..

On Sunday, 7 April 2019 16:20:13 UTC+7, Tim Graham wrote:
>
> MariaDB is supported (see https://code.djangoproject.com/ticket/29548). 
> The test failures are (as the error message says) because you haven't 
> installed the timezone definitions.
>
> On Sunday, April 7, 2019 at 3:03:14 AM UTC-4, Asif Saif Uddin wrote:
>>
>> You can open a work in progress pr to fix them one by one gradually and 
>> trying to fix some of them will give you a much better understanding of 
>> django orm internals as it is considered the most complex part of the 
>> framework. This will also improve your chance to represent yourself as a 
>> much stronger candidate and you will be able to interact with the community 
>> in a very meaningful way. Just my 2 cents. 
>>
>> On Sunday, April 7, 2019 at 12:27:51 PM UTC+6, Sage M.A. wrote:
>>>
>>> Oh, I forgot, one of them is not related to datetime functions: 
>>> test_unsupported_backend.
>>>
>>> On Sunday, 7 April 2019 13:26:10 UTC+7, Sage M.A. wrote:
>>>>
>>>> Hi Asif,
>>>> That's a good idea! I've installed the latest stable release of MariaDB 
>>>> (10.3.14) on my machine and ran Django test suits with it.
>>>> The results 
>>>> <https://gist.github.com/laymonage/a6beb3ec49b2633a508e40d2862ce875> (I've 
>>>> truncated them to only contain the failures and errors) show 19 failures 
>>>> and 15 errors, all of which seem to be
>>>> related to datetime functions. I suppose that'll be enough for me to 
>>>> work on if my GSoC project finishes early. I'll also need to
>>>> write docs about the new support for MariaDB.
>>>>
>>>> On a side note, setting up and destroying the database for the test 
>>>> took hours on my machine. Is that normal? I had to use
>>>> verbosity=2 to find out that it was not freezing, just really slow.
>>>>
>>>> On Saturday, 6 April 2019 22:32:53 UTC+7, Asif Saif Uddin wrote:
>>>>>
>>>>> Sage, regarding MariaDB, I have a little suggestion with you. If you 
>>>>> could setup a latest version of mariadb locally and try to run Django 
>>>>> test 
>>>>> 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.
>>>>>>
>>>>>> 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 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 week from the merging process into writing the 
>>>>>>aforementioned docs.
>>>>>>- Wrote about the possibility of merging the first and second 
>>>>>>milestones so the final milestone would not be so big to merge. (see 
>>>>>> 3.1.2 
>>>>>>and 3.2.2)
>>>>>>- Wrote about the possibility of finishing the project early (see 
>>>>>>3.4)
>>>>>>
>>>>>> About #29548 <https://code.djangoproject.com/ticket/29548>, it seems 
>>>>>> interesting to me but I'm not quite sure what's left to be done.
>>>>>>
>>>>>> Regards,
>>>>>> Sage
>>>>>>
>>>>>> On Wednesday, 3 April 2019 21:40:09 UTC+7, Carlton Gibson wrote:
>>>>>>>
>>>>>>> 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
>>>>>>

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

[Sage M.A.]

Thanks for the information Asif, but it turns out Django already supports 
MariaDB.

On Sunday, 7 April 2019 14:03:14 UTC+7, Asif Saif Uddin wrote:
>
> You can open a work in progress pr to fix them one by one gradually and 
> trying to fix some of them will give you a much better understanding of 
> django orm internals as it is considered the most complex part of the 
> framework. This will also improve your chance to represent yourself as a 
> much stronger candidate and you will be able to interact with the community 
> in a very meaningful way. Just my 2 cents. 
>
> On Sunday, April 7, 2019 at 12:27:51 PM UTC+6, Sage M.A. wrote:
>>
>> Oh, I forgot, one of them is not related to datetime functions: 
>> test_unsupported_backend.
>>
>> On Sunday, 7 April 2019 13:26:10 UTC+7, Sage M.A. wrote:
>>>
>>> Hi Asif,
>>> That's a good idea! I've installed the latest stable release of MariaDB 
>>> (10.3.14) on my machine and ran Django test suits with it.
>>> The results 
>>> <https://gist.github.com/laymonage/a6beb3ec49b2633a508e40d2862ce875> (I've 
>>> truncated them to only contain the failures and errors) show 19 failures 
>>> and 15 errors, all of which seem to be
>>> related to datetime functions. I suppose that'll be enough for me to 
>>> work on if my GSoC project finishes early. I'll also need to
>>> write docs about the new support for MariaDB.
>>>
>>> On a side note, setting up and destroying the database for the test took 
>>> hours on my machine. Is that normal? I had to use
>>> verbosity=2 to find out that it was not freezing, just really slow.
>>>
>>> On Saturday, 6 April 2019 22:32:53 UTC+7, Asif Saif Uddin wrote:
>>>>
>>>> Sage, regarding MariaDB, I have a little suggestion with you. If you 
>>>> could setup a latest version of mariadb locally and try to run Django test 
>>>> 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.
>>>>>
>>>>> 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 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 week from the merging process into writing the 
>>>>>aforementioned docs.
>>>>>- Wrote about the possibility of merging the first and second 
>>>>>milestones so the final milestone would not be so big to merge. (see 
>>>>> 3.1.2 
>>>>>and 3.2.2)
>>>>>- Wrote about the possibility of finishing the project early (see 
>>>>>3.4)
>>>>>
>>>>> About #29548 <https://code.djangoproject.com/ticket/29548>, it seems 
>>>>> interesting to me but I'm not quite sure what's left to be done.
>>>>>
>>>>> Regards,
>>>>> Sage
>>>>>
>>>>> On Wednesday, 3 April 2019 21:40:09 UTC+7, Carlton Gibson wrote:
>>>>>>
>>>>>> 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 timeline: I think you've spread the coding bit too thin 
>>>>>>and not allocated enough for Documenting.
>>>>>>   - I think you if you want full-guns at the SQLite PoC in week 
>>>>>>   1 and 2 you'd have something in place quite quickly. 
>>>>>>  - The base field should be simple enough™
>>>>>>  - The SQLite only lookups shouldn't be too complicated. 

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

[Sage M.A.]

Oh, I forgot, one of them is not related to datetime functions: 
test_unsupported_backend.

On Sunday, 7 April 2019 13:26:10 UTC+7, Sage M.A. wrote:
>
> Hi Asif,
> That's a good idea! I've installed the latest stable release of MariaDB 
> (10.3.14) on my machine and ran Django test suits with it.
> The results 
> <https://gist.github.com/laymonage/a6beb3ec49b2633a508e40d2862ce875> (I've 
> truncated them to only contain the failures and errors) show 19 failures 
> and 15 errors, all of which seem to be
> related to datetime functions. I suppose that'll be enough for me to work 
> on if my GSoC project finishes early. I'll also need to
> write docs about the new support for MariaDB.
>
> On a side note, setting up and destroying the database for the test took 
> hours on my machine. Is that normal? I had to use
> verbosity=2 to find out that it was not freezing, just really slow.
>
> On Saturday, 6 April 2019 22:32:53 UTC+7, Asif Saif Uddin wrote:
>>
>> Sage, regarding MariaDB, I have a little suggestion with you. If you 
>> could setup a latest version of mariadb locally and try to run Django test 
>> 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.
>>>
>>> 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 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 week from the merging process into writing the 
>>>aforementioned docs.
>>>- Wrote about the possibility of merging the first and second 
>>>milestones so the final milestone would not be so big to merge. (see 
>>> 3.1.2 
>>>and 3.2.2)
>>>- Wrote about the possibility of finishing the project early (see 
>>>3.4)
>>>
>>> About #29548 <https://code.djangoproject.com/ticket/29548>, it seems 
>>> interesting to me but I'm not quite sure what's left to be done.
>>>
>>> Regards,
>>> Sage
>>>
>>> On Wednesday, 3 April 2019 21:40:09 UTC+7, Carlton Gibson wrote:
>>>>
>>>> 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 timeline: I think you've spread the coding bit too thin 
>>>>and not allocated enough for Documenting.
>>>>   - I think you if you want full-guns at the SQLite PoC in week 1 
>>>>   and 2 you'd have something in place quite quickly. 
>>>>  - The base field should be simple enough™
>>>>  - The SQLite only lookups shouldn't be too complicated. 
>>>>   - As I commented on the other thread on this topic, we'll need 
>>>>   to advise on getting people set up with SQLite with the JSON 
>>>> extension. 
>>>>   - There's more in this that you think I'd guess. No harm in 
>>>>  putting time in the schedule for it. 
>>>>   - Allow for the possibility you complete early and have time to 
>>>>   work on other things...
>>>>   - This stuff is difficult to get right. It's more balance that 
>>>>   exact times: 
>>>>  - The actual timeline won't match the plan ever. 
>>>>  - you don't need to worry about two days off for holiday 
>>>>   
>>>> Your contributions so far have been super. Thank you. 
>>>>
>>>> Kind Regards,
>>>>
>>>> Carlton
>>>>
>>>>
>>>> On Tuesday, 2 April 2019 13:41:37 UTC+2, 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 
>>>

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

[Sage M.A.]

Hi Asif,
That's a good idea! I've installed the latest stable release of MariaDB 
(10.3.14) on my machine and ran Django test suits with it.
The results 
<https://gist.github.com/laymonage/a6beb3ec49b2633a508e40d2862ce875> (I've 
truncated them to only contain the failures and errors) show 19 failures 
and 15 errors, all of which seem to be
related to datetime functions. I suppose that'll be enough for me to work 
on if my GSoC project finishes early. I'll also need to
write docs about the new support for MariaDB.

On a side note, setting up and destroying the database for the test took 
hours on my machine. Is that normal? I had to use
verbosity=2 to find out that it was not freezing, just really slow.

On Saturday, 6 April 2019 22:32:53 UTC+7, Asif Saif Uddin wrote:
>
> Sage, regarding MariaDB, I have a little suggestion with you. If you could 
> setup a latest version of mariadb locally and try to run Django test 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.
>>
>> 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 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 week from the merging process into writing the 
>>aforementioned docs.
>>- Wrote about the possibility of merging the first and second 
>>milestones so the final milestone would not be so big to merge. (see 
>> 3.1.2 
>>and 3.2.2)
>>- Wrote about the possibility of finishing the project early (see 3.4)
>>
>> About #29548 <https://code.djangoproject.com/ticket/29548>, it seems 
>> interesting to me but I'm not quite sure what's left to be done.
>>
>> Regards,
>> Sage
>>
>> On Wednesday, 3 April 2019 21:40:09 UTC+7, Carlton Gibson wrote:
>>>
>>> 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 timeline: I think you've spread the coding bit too thin and 
>>>not allocated enough for Documenting.
>>>   - I think you if you want full-guns at the SQLite PoC in week 1 
>>>   and 2 you'd have something in place quite quickly. 
>>>  - The base field should be simple enough™
>>>  - The SQLite only lookups shouldn't be too complicated. 
>>>   - As I commented on the other thread on this topic, we'll need to 
>>>   advise on getting people set up with SQLite with the JSON extension. 
>>>   - There's more in this that you think I'd guess. No harm in 
>>>  putting time in the schedule for it. 
>>>   - Allow for the possibility you complete early and have time to 
>>>   work on other things...
>>>   - This stuff is difficult to get right. It's more balance that 
>>>   exact times: 
>>>  - The actual timeline won't match the plan ever. 
>>>  - you don't need to worry about two days off for holiday 
>>>   
>>> Your contributions so far have been super. Thank you. 
>>>
>>> Kind Regards,
>>>
>>> Carlton
>>>
>>>
>>> On Tuesday, 2 April 2019 13:41:37 UTC+2, 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 to Django. I have written a 
>>>> draft for my proposal in this gist 
>>>> <https://gist.github.com/laymonage/b53a1acbbab36b6cd526b48fd2a5>. 
>>>> I have submitted two small patches for Django, and I hope to contribute 
>>>> more in the future. Feedbacks are much appreciated, thanks!
>>>>
>>>

-- 
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 to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/f8467086-201f-4cab-b844-b06ca303660d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sage M.A.]

Hi, Carlton.

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 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 week from the merging process into writing the 
   aforementioned docs.
   - Wrote about the possibility of merging the first and second milestones 
   so the final milestone would not be so big to merge. (see 3.1.2 and 3.2.2)
   - Wrote about the possibility of finishing the project early (see 3.4)

About #29548 <https://code.djangoproject.com/ticket/29548>, it seems 
interesting to me but I'm not quite sure what's left to be done.

Regards,
Sage

On Wednesday, 3 April 2019 21:40:09 UTC+7, Carlton Gibson wrote:
>
> 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 timeline: I think you've spread the coding bit too thin and 
>not allocated enough for Documenting.
>   - I think you if you want full-guns at the SQLite PoC in week 1 and 
>   2 you'd have something in place quite quickly. 
>  - The base field should be simple enough™
>  - The SQLite only lookups shouldn't be too complicated. 
>   - As I commented on the other thread on this topic, we'll need to 
>   advise on getting people set up with SQLite with the JSON extension. 
>   - There's more in this that you think I'd guess. No harm in putting 
>  time in the schedule for it. 
>   - Allow for the possibility you complete early and have time to 
>   work on other things...
>   - This stuff is difficult to get right. It's more balance that 
>   exact times: 
>  - The actual timeline won't match the plan ever. 
>  - you don't need to worry about two days off for holiday 
>   
> Your contributions so far have been super. Thank you. 
>
> Kind Regards,
>
> Carlton
>
>
> On Tuesday, 2 April 2019 13:41:37 UTC+2, 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 to Django. I have written a 
>> draft for my proposal in this gist 
>> <https://gist.github.com/laymonage/b53a1acbbab36b6cd526b48fd2a5>. I 
>> have submitted two small patches for Django, and I hope to contribute more 
>> in the future. Feedbacks are much appreciated, thanks!
>>
>

-- 
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 to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/f4565ae9-8dc7-4e2d-a0ac-8ea6ce5d0d76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sage M.A.]

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 
<https://groups.google.com/forum/#!forum/django-users> or the #django 
channel on IRC. I'm sure the community
will be able to help you. I also join those rooms when I can. If you 
actually meant to ask questions about Django
*itself*, then I guess you could ask your questions by posting a new topic 
in this django-developers 
<https://groups.google.com/forum/#!forum/django-developers> forum instead
of this topic. This topic is meant to be a place for me to gather feedbacks 
for my GSoC proposal.
Thank you for your interest :)

On Wednesday, 3 April 2019 18:32:03 UTC+7, sagar ninave wrote:
>
> 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 matter will be
>
> On Wed, Apr 3, 2019 at 8:16 AM Sage M.A. > 
> wrote:
>
>> 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 
>> <https://code.djangoproject.com/ticket/30294> and #30295 
>> <https://code.djangoproject.com/ticket/30295>), and I'm looking to 
>> contribute more in the future.
>>
>> On Wednesday, 3 April 2019 04:12:52 UTC+7, sagar ninave wrote:
>>>
>>> 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 (Contributions to Django itself)" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to django-d...@googlegroups.com.
>>>> To post to this group, send email to django-d...@googlegroups.com.
>>>> Visit this group at https://groups.google.com/group/django-developers.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/django-developers/b02ac6c4-7db3-4d3a-ae08-d1fa848b4b68%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/django-developers/b02ac6c4-7db3-4d3a-ae08-d1fa848b4b68%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> -- 
>> 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-d...@googlegroups.com .
>> To post to this group, send email to django-d...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/3737f569-263d-4d09-acb2-2fdc1e2bebf8%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-developers/3737f569-263d-4d09-acb2-2fdc1e2bebf8%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/a3684f5b-265e-430f-b18f-77f26450716f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sage M.A.]

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 
<https://code.djangoproject.com/ticket/30294> and #30295 
<https://code.djangoproject.com/ticket/30295>), and I'm looking to 
contribute more in the future.

On Wednesday, 3 April 2019 04:12:52 UTC+7, sagar ninave wrote:
>
> 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 (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-d...@googlegroups.com .
>> To post to this group, send email to django-d...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/b02ac6c4-7db3-4d3a-ae08-d1fa848b4b68%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-developers/b02ac6c4-7db3-4d3a-ae08-d1fa848b4b68%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/3737f569-263d-4d09-acb2-2fdc1e2bebf8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sage M.A.]

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 from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/b02ac6c4-7db3-4d3a-ae08-d1fa848b4b68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sage M.A.]

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 with IS JSON 
constraint, and arrays are a valid JSON value.
https://docs.oracle.com/en/database/oracle/oracle-database/18/adjsn/overview-of-storage-and-management-of-JSON-data.html

About HStore, yes, it's not widely used but it's basically just a flat (not 
nested) JSON.

As to why I want to port those field types, to be honest, I don't really 
think it's necessary, but they're nice to have.
However, the idea 
<https://code.djangoproject.com/wiki/SummerOfCode2019#AddCross-DBJSONFieldetc> 
listed on Django's GSoC 2019 page says that those fields would be desirable.
Those two fields would not be my main priority, and I guess maybe their 
implementations could be optional.


On Tuesday, 2 April 2019 19:26:28 UTC+7, Michal Petrucha wrote:
>
> -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 to Django. I have written a 
> > draft for my proposal in this gist 
> > <https://gist.github.com/laymonage/b53a1acbbab36b6cd526b48fd2a5>. I 
> > have submitted two small patches for Django, and I hope to contribute 
> more 
> > in the future. Feedbacks are much appreciated, thanks! 
>
> Hi Sage, 
>
> I'm curious about your intention to implement ArrayField and 
> HStoreField for other databases – you don't really go into any detail 
> about those. Are those types even supported by other SQL databases 
> than Postgres? I can't find any hstore or array type for mysql, for 
> instance, let alone sqlite, and it's been my understanding that these 
> types are pretty specific to Postgres. 
>
> Could you explain in more detail why and how you want to port those 
> field types? 
>
> Michal 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1 
>
> iQIcBAEBCgAGBQJco09GAAoJEHA7T/IPM/klB6oP/2I1TaEFG/SzRh5ArjTEzH60 
> Nd46at1133iJEL/QEz1SzFFkoXT7uRe+71aJroW8NE4KUEXN4giOO/jjhAYB74cv 
> Rzxay45r03g7Io+labwe0ZBIMhfhKRbk+8W4QVyHY8yfZklazwiswRy/3zJENoA4 
> GqML3yQ/0oq72pQtHHbhALp5FCcE5kILadCoYMqJ3BrqQEt5aWi3oQWoIYBCqkXF 
> zV3aM8cH4xsLVHG28646Eu10o5vsf06poYxOpQpF7OwfMy0k2mAjQyfVCeZ6qJzX 
> 2aQpimgjiICBD21Asme4kBUEBmxdGiAiz15zQlnZBW+JeXzQsCFqUf+/T6PqTeyU 
> 0uiX4O8/LhW+4PRG/aXLszcgqsDGOwFk3OstcrI3d+BlJ39ZCM0Kv7Y6L8H5DYKm 
> g9IfMeqD2c+/QECG3tEMhtJwhrvMsxod3Upq+6DhtK3G7xxemlRHjEvOIr/EmV8X 
> I9HRAU5ZmbE1piwZx45oTOD9ZCI2HsQtHuJ6jVsF2mwgdL3FdRGrLqCb2TPV/61x 
> 0P1ehjukYU5fBcdua/2sgD1nRjzQBw54yhlwaTiUoL82JmLoW8tzKCG6mycMfbtY 
> TfXG9wP7Ig+mWYcRdINoM83NSaVQG+Fi98KxJoW/3BFpk3mz4QGrMBLFbs6P3ANc 
> 9+IFrRA/wvJW2+jjBtqo 
> =8GaE 
> -END PGP SIGNATURE- 
>

-- 
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 to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/011a381d-4cfd-4c15-953c-0aff65daf987%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Sage M.A.]

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 
. I 
have submitted two small patches for Django, and I hope to contribute more 
in the future. Feedbacks are much appreciated, thanks!

-- 
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 to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/b5a29506-4a41-43a5-9ce0-2a91c02becfe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal

[Sage M.A.]

Thank you! I'll share my proposal here when I'm done with my first draft.

On Thursday, 28 March 2019 21:49:36 UTC+7, Carlton Gibson wrote:
>
> Hi Sage. 
>
> Yes. It never hurts to apply. If we get two good proposals for the same 
> project, we can find a way to share or another project. 
> We can cross that bridge as and when we come to it. 
> ("Scale later" )
>
> Kind Regards,
>
> Carlton
>
>
> On Thursday, 28 March 2019 14:58:15 UTC+1, Sage M.A. wrote:
>>
>> Hi everyone,
>> Sorry to ask this, but can I also take a shot in this one? I've been 
>> interested in this issue since early February.
>>
>> On Thursday, 21 March 2019 22:28:41 UTC+7, Carlton Gibson wrote:
>>>
>>> Also, sorry, this was the key thread here, plus links therein 
>>> https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion
>>>
>>> On Thursday, 21 March 2019 16:27:14 UTC+1, Carlton Gibson wrote:
>>>>
>>>> Hey Marcio. 
>>>>
>>>> If you can demonstrate that your abilities are sufficient in your 
>>>> proposal, I'm sure we can mentor you through the pull request bit. (It's 
>>>> just "contributor" implies knowledge of the internals, and the ORM **is** 
>>>> the scariest bit, so... it's a bit  this close to starting.) 
>>>>
>>>> You've read the contributing guide right, and had a mooch around? Jump 
>>>> in! https://docs.djangoproject.com/en/dev/internals/contributing/
>>>>
>>>>
>>>> On the Timeline 
>>>> <https://summerofcode.withgoogle.com/how-it-works/#timeline> applications 
>>>> go from 25/3 to 9/4 so there's time to work on a draft, but Tim's right, 
>>>> we 
>>>> do need that effort. 
>>>>
>>>> Standout areas for me:
>>>>
>>>> 1. So we ship a JSONField. With SQLite in mind, most people can't use 
>>>> it, so we need a How-To of some kind on compiling SQLite   with the json1 
>>>> extension and putting it in the right place so Python can find it. 
>>>> 2. For the SQLite PoC, I'd like to see a more aggressive timeline right 
>>>> at the beginning. The base field with save and load shouldn't be Too Hard™ 
>>>> (c.f. jsonb.py 
>>>> <https://github.com/django/django/blob/0b8abd7cdf1a5bae96dd0640af10ad504f104d06/django/contrib/postgres/fields/jsonb.py#L30-L83>
>>>> )
>>>>
>>>> The issue is (3) the lookups and how to handle integrating those with 
>>>> the existing postgres ones, the MySQL package and, the Oracle example. 
>>>> A decent sketch of an answer there and we have a proposal I think. 
>>>>  (Maybe it's an simple as `as_sqlite()`, `as_oralce()` etc, as with the 
>>>> existing functions implementations, but...) 
>>>>
>>>> Kind Regards,
>>>>
>>>> Carlton
>>>>
>>>>

-- 
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 to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/5bc96405-f23c-4c6b-9580-767fd9710da1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal

[Sage M.A.]

Hi everyone,
Sorry to ask this, but can I also take a shot in this one? I've been 
interested in this issue since early February.

On Thursday, 21 March 2019 22:28:41 UTC+7, Carlton Gibson wrote:
>
> Also, sorry, this was the key thread here, plus links therein 
> https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion
>
> On Thursday, 21 March 2019 16:27:14 UTC+1, Carlton Gibson wrote:
>>
>> Hey Marcio. 
>>
>> If you can demonstrate that your abilities are sufficient in your 
>> proposal, I'm sure we can mentor you through the pull request bit. (It's 
>> just "contributor" implies knowledge of the internals, and the ORM **is** 
>> the scariest bit, so... it's a bit  this close to starting.) 
>>
>> You've read the contributing guide right, and had a mooch around? Jump 
>> in! https://docs.djangoproject.com/en/dev/internals/contributing/
>>
>>
>> On the Timeline 
>>  applications 
>> go from 25/3 to 9/4 so there's time to work on a draft, but Tim's right, we 
>> do need that effort. 
>>
>> Standout areas for me:
>>
>> 1. So we ship a JSONField. With SQLite in mind, most people can't use it, 
>> so we need a How-To of some kind on compiling SQLite   with the json1 
>> extension and putting it in the right place so Python can find it. 
>> 2. For the SQLite PoC, I'd like to see a more aggressive timeline right 
>> at the beginning. The base field with save and load shouldn't be Too Hard™ 
>> (c.f. jsonb.py 
>> 
>> )
>>
>> The issue is (3) the lookups and how to handle integrating those with the 
>> existing postgres ones, the MySQL package and, the Oracle example. 
>> A decent sketch of an answer there and we have a proposal I think. 
>>  (Maybe it's an simple as `as_sqlite()`, `as_oralce()` etc, as with the 
>> existing functions implementations, but...) 
>>
>> Kind Regards,
>>
>> Carlton
>>
>>

-- 
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 to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/bf8de3b1-a444-40ce-8c9b-8397cd0eab5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.