I've been away from these efforts for a while, but someone interested in bridging SQL/NoSQL in Django might find these links interesting:
http://msdn.microsoft.com/library/bb308959.aspx http://cacm.acm.org/magazines/2011/4/106584-a-co-relational-model-of-data-for-large-shared-data-banks/fulltext http://unqlspec.org/display/UnQL/Syntax+Summary On Thu, Aug 11, 2011 at 8:51 PM, Russell Keith-Magee < [email protected]> wrote: > On Fri, Aug 12, 2011 at 11:25 AM, Nathan Hoad <[email protected]> > wrote: > > Hi guys, just wondering what the status is on the official NoSQL > > support? I've done a lot of reading and the last official post I can > > see is Alex Gaynor's GSoC post, from August last year mentioning the > > Query refactor and how it should help down the road for NoSQL, but > > nothing past that. > > There are two efforts in play here: > > 1) The "official" effort, that was largely worked on during the GSoC last > year > > 2) The "unofficial" effort, largely the work of the guys at All > Buttons Pressed. See > http://www.allbuttonspressed.com/projects/django-nonrel for details. > > (I use "official" in quotes because I don't want to imply that the > "unofficial" port is broken in some way or that the "official" port is > better -- just that the "unofficial" version hasn't been developed > without any particular core team involvement. The reported feature set > of the "unofficial" branch is certainly more advanced than the > "official" branch) > > The progress on these two efforts (from the perspective of the Django > core) has been stalled, for different reasons. > > The "official" effort has stalled because Alex hasn't been actively > pursuing the branch; there are some good ideas in the branch, but > there are also a couple of big design issues that need to be made > before the branch would be a candidate for merging (such as how to > deal with non-integer autofields). See the mailing list discussions > for more details on these problems. > > The "unofficial" effort is being actively worked on (AFAIK), but the > impediment on getting it near core is a lack of external review. > Despite repeated calls for independent review of the internals, none > has been forthcoming. > > Speaking personally: I've only had one report from someone I trust > that has used django-nonrel; and I haven't seen a good analysis of > "how it does what it does". NoSQL isn't a huge priority for me > personally, and so addressing other problems has taken a priority. I > think it's safe to assume the same is true of the other core > developers. > > > Basically, I'm just wondering what, if anything, is being done about > > it? > > Is there a core developer actively working on the topic right now? Not > to my knowledge. > > Is the core team interested in getting NoSQL support into trunk? > Absolutely -- if it can be done without compromising the rest of > Django's ORM, and if members of the community can work together to > either: > 1) resolve the issues in the "official" branch, or > 2) build the social trust around the "unofficial" branch to show that > it warrants inclusion in trunk. > > Yours > Russ Magee %-) > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
