On Wed, Aug 25, 2010 at 2:04 AM, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Wed, Aug 25, 2010 at 3:57 AM, Waldemar Kornewald > <wkornew...@gmail.com> wrote: >> On Aug 24, 9:30 pm, mack the finger <nbvf...@gmail.com> wrote: >>> I'm considering starting a project, and am leaning towards using >>> google app engine instead of the traditional LAMP stack. The problem >>> is that with app engine, you can't use django models, or anything else >>> that depends on django models, which means no modelforms, no admin, no >>> authentication, no third party-apps, etc. This is a huge drawback for >>> me. >>> >>> Lately there has been some work getting non-relational databases >>> working with django. In lieu of all of that, what is the likelihood >>> that in the near future django will grow the ability to work more >>> natively with app engine? >> >> Django-nonrel with djangoappengine is what you're searching for: >> http://www.allbuttonspressed.com/projects/django-nonrel >> http://www.allbuttonspressed.com/projects/djangoappengine >> >> With that combo you can use Django's models on App Engine (which >> includes modelforms, admin, auth, etc.). 3rd-party apps like django- >> socialauth work, too, but apps which depend on JOINs won't work >> because the App Engine datastore doesn't support JOINs. We do plan to >> solve that, too, but that'll take some time. >> >> Then, when Django 1.3 gets official nonrel support we'll port >> djangoappengine to that, so you can continue to use your code, but >> this time with the official Django release. > > Firstly -- Nobody has ever committed to getting Alex's query-refactor > branch merged in for Django 1.3. In fact, I'm on record in at least > one forum (DC.eu) saying "Almost certainly not before 1.4". As Alex > described in his end of GSoC announcement, there are still some loose > ends that need to be resolved, and the timeframe for the 1.3 release > doesn't provide enough time to get this stuff merged in time for a > feature freeze.
The only big issue I can see is AutoField. It doesn't really matter if the first release of Django has ListField support for PostgreSQL. What matters is that nonrel backends have ListField. Even EmbeddedDocument is not a MUST for the first release. The point of the first release is to start the community building process, so at the time of the 1.4 release you have enough people and enough features. You can label this as the low-level preparation towards full nonrel support with the purpose of attracting backend authors for 1.4. Please don't wait until it's perfect and you have 100% features because (1) then people will have a nice ORM, but no backends, and (2) you'll be developing the ORM almost "blind" without real-world feedback. Fix AutoField and get this thing out, so people can give you real-world feedback and start writing backends. > Secondly -- One of the reasons that this isn't going to happen for 1.4 > is that we're not going to rush it. Aside from fixing the loose ends, > we need to be convinced that the changes that Alex has made are > sufficient to support multiple non-relational backends. So far, he's > got a compelling proof of concept with MongoDB; however, I need to see > similar proofs of concept for other stores (CouchDB, Cassandra and GAE > would be my ideal list) before I'm convinced that the proposed changes > are sufficient. As Alex' MongoDB backend demonstrates, all nonrel backends can retrieve the Query's filters. With this they can fetch or count the matching entities. What kind of problems do you expect with other backends? Why would CouchDB not be able to retrieve the filters? And if all backends can get the filters then what else could cause problems, at all? The only problem is to convert the filters into the DB's query language, but this has absolutely nothing to do with Django's ORM. I can port the GAE backend pretty quickly if this is a prerequisite to getting it into 1.3. But I really don't see why yet another backend (after the GAE backend port) would make you more convinced. The ORM merely needs to provide the filters and the backend merely needs to provide the result rows. All of this already works. Bye, Waldemar Kornewald -- Django on App Engine, MongoDB, ...? Browser-side Python? It's open-source: http://www.allbuttonspressed.com/blog/django -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
