Re: [elephant-devel] Good practices around adding/deleting class slots.

2009-01-11 Thread quan hu
Hi Yarek, Regarding to data migration, it is migration between different stores. My understanding of the typical cases are: 1. Change the backend. e.g. change BDB to Postmodern . 2. Upgrade. e.g. your application uses elephant 0.9.1 and BDB 4.5; To upgrade elephant from 0.9.1

Re: [elephant-devel] Good practices around adding/deleting class slots.

2009-01-08 Thread Ian Eslick
Hi Yarek, There are no problems adding or deleting slots. The semantics are basically the same as redefining slots for standard classes. You can change the type of a slot (e.g. cached, index, etc) without any data loss. If you change the name or drop a slot the data associated with that

[elephant-devel] Good practices around adding/deleting class slots.

2009-01-08 Thread Yarek Kowalik
In an evolving site there is a fair chance of adding/changing/deleting slots from a class. What are good practices with respect to these actions in Elephant? Are there specific steps that need to be taken to migrate data from an old class definition to a new class definition? Any gotchas one nee