e've started a supported/unsupported feature list on djangopackages:
http://www.djangopackages.com/grids/g/cloud/
So please help in order to get closer at least one step towards NoSQL
in Django.
Bye,
Thomas Wanschik
--
You received this message because you are subscribed to the Google Groups
"
On Apr 9, 9:06 am, Russell Keith-Magee wrote:
> No - Array types aren't available everywhere. However, it would be
> nice to be able to support them (even if not in core); if this GSoC
> lays the groundwork to make this possible, then it's worth looking at.
We already implemented a ListField in d
made a good step
towards even supporting non-relational databases. Such databases can
use a compiler which can interpret SQL.Query. We thing that only minor
modifications are needed to be completly SQL independent and to be
abstract enough for non-relational databases. Following the QueryData
pr
and if you're currently busy with finishing 1.2, but if
> you're interested in helping when will you have time?
>
Is nobody out there with a little bit of time/interest in helping?
It would be really nice and would speed up the development of
supporting non-relational databases
On 22 Okt., 23:52, Russell Keith-Magee wrote:
> On Fri, Oct 23, 2009 at 5:09 AM, Thomas Wanschik
>
> wrote:
>
> >> When a new QuerySet is instantiated (e.g. by calling
> >> Model.objects.all()) it asks the backend for its Query class and then
> >> create
I just want to remind contributers to fill in the cell "Assigned to"
and "Status" in the task spreadsheet while working on a specific task
in order to prefend problems.
Here is the link:
https://spreadsheets.google.com/ccc?key=0AnLqunL-SCJJdE1fM0NzY1JQTXJuZGdEa0huODVfRH
7;ve also disabled SQL support.
>
> The next step is to move all the hacks into a nice backend API (at the
> same time making sure that it won't conflict with multi-db) and
> re-enable SQL support. That's where we need help. Also, if you want to
> work on SimpleDB s
