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/
>
> 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-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=.


Reply via email to