Sorry, just noticed this. Yeah, schema changes really don't seem to have been a design consideration for the JDO/datanucleus integration. If you want help with JDO, best to describe the exact changes you are making.
If you want to port to Objectify, it shouldn't be too hard since Objectify directly models the low-level data. It will probably be just rote replacement of your JDO calls. How much work this is just depends on how much code you have. Jeff On Sat, Jul 30, 2011 at 9:47 PM, miwcoder <[email protected]> wrote: > Hi, > We are in the process of going live with our app but struggling > with schema changes. We intentionally adopted JDO as we wanted to keep > changes minimum in case we need to port. But it is biting us now as it > is a nightmare to change the schema. We are trying to add only Object > types as suggested in one stackoverflow post but the changes still > throws tons of exceptions. > > How do we handle it? Also is Objectify the only way out? If so how > much work it is to port objectify code? > > any help is appreciated. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
