I would have added d) use an embedded rdbms, and do own consistency If there was a way to control running instances like in EC2....
On Nov 25, 5:17 pm, "K.Honsali" <[email protected]> wrote: > Hi all, > > If my understanding of previous discussions is correct, we can resume > from: > - GAE/J is not relational (not full JDO too), and hence does not > support sql features such as joins, like, not in ...etc > - the solution is to de-normalize your tables ... or your mind.. > > Now, suppose you have a quite big classic sql-based webapp which is > multi-layered like a burger, so it is OK to change the Data Access > Layer without affecting the other components, provided that the DAL > calls and outputs remain the same. > If you want to migrate this app to GAE/J, how would you do; knowing > that beside CRUD queries, you have queries that execute (on the fly w/ > sql) up to a dozen joins ? > a ) re-write your DAL in GAE/J's JDO, by denormalizing your tables (& > your mind) > b ) write your own sql wrapper, using full JDO and the low level > datastore (can it be?) > c ) none of the above > > Thanks for your CPU time :) -- 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.
