sqlobject could probably simulate joins the hard way as well.....it might not be that bad performance wise at least for some apps in some cases.

On Wed, Apr 9, 2008 at 2:27 PM, Daniel Fetchinson <fetchinson@googlemail.com> wrote:
> Any interest in developing a google app engine backend for sqlobject?
> See http://code.google.com/appengine/docs/datastore/
>    Only if someone does the job. And with the following caveats:
> -- I don't know if the docs provide enough information about low-level
>    details; currently I see the docs mostly concentrated on Django ORM,
>    I don't know if it's possible to write an SQLObject connection class at
>    all;
> -- this is a commercial storage that I don't have a test access to, so the
>    driver will always be underdeveloped and undertested unless someone
>    provides a steady stream of patches - a situation similar to
>    "second-class citizens" of SQLObject like Sybase and MaxDB.
> Oleg.
>   The Google AppEngine appears to use Bigtable
> (http://labs.google.com/papers/bigtable.html).
> This is not a relational database.
> However, I get the impression from the "Camp Fire" that free access is
> available for development and testing.

Yes, it's not a relational database, but in practice all this means is
that you can not make joins (I think). You can still query a single
table for various properties, order the result, and iterate over them.
There are one-to-many and many-to-many relationships too. So it seems
to me that a good portion of sqlobject is applicable but of course
certain parts will have no meaning (like joins).

I've already signed up for an account but haven't heard back from them yet.


This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
sqlobject-discuss mailing list