Archived
This forum has been archived. Please start a new discussion on GitHub.
Freeze::Map and versioning
Hi,
I'd like to collect some long-term statistics about remote processes. I thought that using the Freeze::Map might be a good way of getting persistence with minimal effort on my behalf, since the datatypes I want to collect are already slice-defined anyway.
This was surprisingly easy, I had a network-enabled database up and running in no time!
My only question is about future changes: I can envision that at some point down the track one or more of my slice-defined datatypes is likely to change. Does anyone have any insights into what might be the best/easiest way of migrating my existing database when this happens?
Thanks,
Alex
I'd like to collect some long-term statistics about remote processes. I thought that using the Freeze::Map might be a good way of getting persistence with minimal effort on my behalf, since the datatypes I want to collect are already slice-defined anyway.
This was surprisingly easy, I had a network-enabled database up and running in no time!
My only question is about future changes: I can envision that at some point down the track one or more of my slice-defined datatypes is likely to change. Does anyone have any insights into what might be the best/easiest way of migrating my existing database when this happens?
Thanks,
Alex
0
Comments
-
Check out the chapter about FreezeScript in the manual. It explains how to migrate databases if you need to modify Slice types.
Cheers,
Michi.0 -
Sweet, I hadn't seen that at all -- thanks.0
