In NoSQL, you don't have join as you said.
In NoSQL, managing data is more direct than RDBMS but when you want to merge
data from different tables, you need to do it yourself in your app. In a
summary, for relations, you do the job of the DB. So, this might seem a
drawback but it's also a big advan
Thanks for all the replies,
just a quick question. Since BigTable is object database so why bother
having relationship between entities? I know there are advantages to that.
But for small application like school project, I think I dont really need to
have all those relationship annotations in relev
Hi,
You don't need to worry much on the underlying of the datastore (big table)
but rather understand how the datastore works as a non relational way of
persisting data in your application. If you are using Java you have:
- JPO: http://code.google.com/appengine/docs/java/datastore/jdo/
- JPA: h
Hi,
BigTable is a NoSQL DB without join feature that you know in SQL.
So you manage relations manually and do join by issuing several request
instead a single one and you join within your application context.
Basically you do more computation in your app than in the DB in this case.
But the DB is m
Hi,
I'm pretty new to this GAE platffrom and the Google BigTable. Ive been
trying to search for tutorial (with example) on this subject but found
nothing to get me started (found handful of Python examples but my app
is to be written in Java). There are few good examples which I have
tried and its
