Why not implement a Django database backend for App Engine?

[frankabel]

Hi all,

I'm newbie in this App Engine. As far I know, lot of Django app
portability get solved if someone implement a Django database backend
for App Engine. Even I read "Once queryset-refactor lands in trunk, it
might also be possible to write a database backend for App Engine that
would allow any app to run properly. " at http://martyalchin.com/2008/apr/8/appengine/

Somebody can explain me why isn't implemented yet such database
backend? I, mean is a big deal? What are the main problems that ones
must address to write such backend? If the backend exist, porting
Django app will be more easy that using Google App Engine Helper for
Django?

Cheers
Frank Abel

[Gabriel Robertson]

Because the datastore is not a database. Some of their operations may
look similar, but they really are not. It is not a direct 1-to-1
mapping, no where near actually.

[sserrano]

While it is a difficult task there is people trying to work around
it.

Follow wkornewald at http://bitbucket.org/wkornewald/ he is doing an
excellent work

Cheers, Sebastian Serrano

http://www.sserrano.com

On 18 nov, 09:54, frankabel <frank.abel...@gmail.com> wrote:
> Hi all,
>
> I'm newbie in this App Engine. As far I know, lot of Django app
> portability get solved if someone implement a  Django database backend
> for App Engine. Even I read "Once queryset-refactor lands in trunk, it
> might also be possible to write a database backend for App Engine that

> would allow any app to run properly. " athttp://martyalchin.com/2008/apr/8/appengine/

[Julian Namaro]

Traditional relational databases are not scalable, and using such
library would most likely result in a data organization that does not
scale well. Might be fine for a lot of apps, but it kind of defeat the
main purpose of using a cloud infrastructure.

On Nov 18, 9:54 pm, frankabel <frank.abel...@gmail.com> wrote:
> Hi all,
>
> I'm newbie in this App Engine. As far I know, lot of Django app
> portability get solved if someone implement a Django database backend
> for App Engine. Even I read "Once queryset-refactor lands in trunk, it
> might also be possible to write a database backend for App Engine that

> would allow any app to run properly. " athttp://martyalchin.com/2008/apr/8/appengine/

[mdipierro]

web2py has a database abstraction layer that works with SQLIte, MySQL,
MSSQL, Oracle, DB2, Informix, Ingres, FireBird, MSSQL, and the Google
App Engine. It also does automatic migrations. You way want to look
into that.

Massimo

On Nov 18, 6:54 am, frankabel <frank.abel...@gmail.com> wrote:
> Hi all,
>
> I'm newbie in this App Engine. As far I know, lot of Django app
> portability get solved if someone implement a  Django database backend
> for App Engine. Even I read "Once queryset-refactor lands in trunk, it
> might also be possible to write a database backend for App Engine that

> would allow any app to run properly. " athttp://martyalchin.com/2008/apr/8/appengine/

[Andy Smith]

I've started working on (or at least at this point only arguing with django people) this project as well, but it is still some time off so I wouldn't hold your breath quite yet.

--

You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Hazzadous]

Search the django-devel group for non-relational db for info on this
topic. Google has apparently set aside some time for this effort.

On Nov 20, 7:34 pm, Andy Smith <andys...@gmail.com> wrote:
> I've started working on (or at least at this point only arguing with django
> people) this project as well, but it is still some time off so I wouldn't
> hold your breath quite yet.
>

> On Wed, Nov 18, 2009 at 11:11 AM, sserrano <sebastian.serr...@gmail.com>wrote:
>
>
>
> > While it is a difficult task there is people trying to work around
> > it.
>

> > Follow wkornewald athttp://bitbucket.org/wkornewald/he is doing an

> > excellent work
>
> > Cheers, Sebastian Serrano
>
> >http://www.sserrano.com
>
> > On 18 nov, 09:54, frankabel <frank.abel...@gmail.com> wrote:
> > > Hi all,
>
> > > I'm newbie in this App Engine. As far I know, lot of Django app
> > > portability get solved if someone implement a  Django database backend
> > > for App Engine. Even I read "Once queryset-refactor lands in trunk, it
> > > might also be possible to write a database backend for App Engine that
> > > would allow any app to run properly. " athttp://
> > martyalchin.com/2008/apr/8/appengine/
>
> > > Somebody can explain me why isn't implemented yet such database
> > > backend? I, mean is a big deal? What are the main problems that ones
> > > must address to write such backend? If the backend exist, porting
> > > Django app will be more easy that using Google App Engine Helper for
> > > Django?
>
> > > Cheers
> > > Frank Abel
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-a...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > google-appengi...@googlegroups.com<google-appengine%2Bunsubscrib e...@googlegroups.com>
> > .

[Hazzadous]

From the django devel group: http://tinyurl.com/y9gpf55

This is probably the most up to date/informative info on non-
relational db support for Django?

On Nov 20, 7:34 pm, Andy Smith <andys...@gmail.com> wrote:

> I've started working on (or at least at this point only arguing with django
> people) this project as well, but it is still some time off so I wouldn't
> hold your breath quite yet.
>

> On Wed, Nov 18, 2009 at 11:11 AM, sserrano <sebastian.serr...@gmail.com>wrote:
>
>
>
> > While it is a difficult task there is people trying to work around
> > it.
>

> > Follow wkornewald athttp://bitbucket.org/wkornewald/he is doing an

> > excellent work
>
> > Cheers, Sebastian Serrano
>
> >http://www.sserrano.com
>
> > On 18 nov, 09:54, frankabel <frank.abel...@gmail.com> wrote:
> > > Hi all,
>
> > > I'm newbie in this App Engine. As far I know, lot of Django app
> > > portability get solved if someone implement a  Django database backend
> > > for App Engine. Even I read "Once queryset-refactor lands in trunk, it
> > > might also be possible to write a database backend for App Engine that
> > > would allow any app to run properly. " athttp://
> > martyalchin.com/2008/apr/8/appengine/
>
> > > Somebody can explain me why isn't implemented yet such database
> > > backend? I, mean is a big deal? What are the main problems that ones
> > > must address to write such backend? If the backend exist, porting
> > > Django app will be more easy that using Google App Engine Helper for
> > > Django?
>
> > > Cheers
> > > Frank Abel
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-a...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > google-appengi...@googlegroups.com<google-appengine%2Bunsubscrib e...@googlegroups.com>
> > .