On 12 Mar 2010, at 19:30, Nacho Coloma wrote:
I have one question more or less related to this thread. Why are both
Objectify and Twig tying the schema upgrade to the persistence
framework? As far as I can recall no persistence framework does this,
and it hasn't been that Hibernate didn't have the chance.
If I am following correctly, you are proposing to specify the
migration path in the persistence metadata, but I just don't get it.
Why?
Because the datastore has no schema the interfaces need to define the
schema themselves - as Java objects and some annotations. So if you
are already defining the schema at the data model level it makes sense
to define changes there too.
Do you mean use the low-level api instead to alter the data? In that
case you still need to configure the interface to read/write the new
format - so may as well reuse it, no?
I do remember something in HIbernate that could generate "update
table" scripts from changed config files. But I guess with all back
ends they had to support it was a much tougher job.
--
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 google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
