No examples, just ideas till now :) We should define a few usecases and look at the existing projects even in SQL world!
Migration between DBs means 2 things IMO: - An existing model evolves (rename field, change type of a field ...) -> this case is certainly the simplest in a first approach - You have an existing DB and need to transform it into another DB by migrating data from the first to the second performing operations on it. A field in the destination DB could be the result of an operation on one or several fields from the originating DB -> this case is much more complex and complete Do you see other cases? Pascal On Wed, Aug 17, 2011 at 6:42 PM, Max <[email protected]> wrote: > sounds good, any plan to start? and any concrete example to look forward? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/MI_jgQyqGkEJ. > > 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.
