> Basically, I have a client program which needs to create tables and > their entities dynamically, so the columns would change over time. > This does not fit well with JDO as it works for fixed column entitys > that are annotated.
Not necessarily. Annotations are just one way of specifying what is persisted. JDO is also the only persistence standard with an API to define what fields are persisted. You could make use of that, as some clients have done, and have everything totally dynamic -- the class generation, the metadata specification, the enhancement, and the persistence http://www.jpox.org/servlet/wiki/pages/viewpage.action?pageId=6619188 Fits very nicely with JDO
-- 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.
