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/b53a1acbbab36b77776cd526b48fd2a5>. >>>> 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.
