Cross-DB JSONField ready for review

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

Re: Fellow Reports -- July 2019

Hi All, Reposting Wks 29-30, in which I inadvertently leaked small details of the then pending security patches. Many thanks to Kevin Grinberg for noticing and advising me quickly. I then deleted the post, which, whilst not ideal, was the best I could do. I've update the command to compi

Re: Cross-DB JSONField ready for review

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 >

Re: Cross-DB JSONField ready for review

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 w

Re: Cross-DB JSONField ready for review

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

Re: Cross-DB JSONField ready for review

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

Re: Cross-DB JSONField ready for review

Hi Sage. Perhaps draft it in a howto and we can have a look once it’s in play. C. On Sat, 3 Aug 2019 at 03:23, Sage M.A. wrote: > 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