> Of course, there are schema changes which are invisible to the class > system, that also need to be accounted for. For example, you represent > user status as an integer (representing an enumerated type.) You decide > to remove a status. The types haven't changed, but the entire schema > has to be massaged into the new set of enumerated types.
This would be the responsbility of the userland part: let the programmer bump the schema's version number to indicate a change and then provide a transition function. > I think the lack of schema evolution is Elephant's biggest problem; but > is there any system that has solved this problem? Let's be the first one. Leslie -- My personal blog: http://blog.viridian-project.de/ _______________________________________________ elephant-devel site list elephant-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/elephant-devel
