On Sep 7, 1:28 pm, datanucleus <[email protected]> wrote:
> Why do you want an ORM exactly ? Object - Relational Mapping ? The
> datastore is BigTable. It isn't an RDBMS.
True. But it's also not object-oriented. So your objects need to be
mapped to the datastore somehow. I think of object/relational mappers
performing that role even if it doesn't apply precisely in the case of
a non-relational data store like Big Table. But I don't know if it's
worth debating this point. I just want to know the best way to get up
and running with a simple framework. Coming from the Ruby world, I'm
used to have an ORM to translate my domain objects to relational
structures in a way that I think is probably close to what Hibernate
does. I was hoping there was a simple Ruby-like equivalent of Rails
+ActiveRecord for the GAE/J world.
> GAE/J comes with JDO/JPA implementations for persistence to that
> datastore.
Ok, thanks. I'm not familiar with JDO/JPA but since you make a point
about there not being a need for an ORM, I will assume for now that
these are some kind of data access objects that carry out the
persistence operations for your domain layer. I have some reading to
do obviously.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en
-~----------~----~----~----~------~----~------~--~---
