I'm facing the exact same problem. Did you find any way to migrate data with PB? The only way I can think of is to keep generated code of each schema version and program the migration with that. The link provided by Alkis treats only cases to add/remove fileds, but that not enough when the structure change.
Vincent On Tuesday, July 8, 2008 at 5:18:28 AM UTC-4, Colin Fleming wrote: > > Hi all, > > Great to see this project, it saves me a bunch of work I was about to > start! I'll need to adapt it a little but it will help me a lot. > > One thing I'd like to see is some support for type/schema modification > and migration. If PB are used only as a network wire format this is > probably not so important, but if you serialise your objects then it > starts to become an issue. Has anyone thought about this? I'm not sure > how this should be encoded - I guess you'd need at a minimum a version > number (probably as the first element) and some conditional code to > deserialise the various forms. I was thinking about using something > similar to what Tangosol recommend here: > > http://wiki.tangosol.com/pages/viewpage.action?pageId=16694 > > But it's a pretty limited solution. Any ideas? Patterns? > > Thanks for any help, > Colin > > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
