Xref: utzoo comp.object:3459 comp.databases:9925 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!tut.cis.ohio-state.edu!sei.cmu.edu!fs7.ece.cmu.edu!o.gp.cs.cmu.edu!netnews.srv.cs.cmu.edu!clamen From: clamen@CS.CMU.EDU (Stewart Clamen) Newsgroups: comp.object,comp.databases Subject: Schema/Type Evolution in Traditional and O-O DBMSs Keywords: type evolution, schema evolution, OODBMS, RDBMS Message-ID: Date: 5 May 91 21:48:01 GMT Sender: netnews@cs.cmu.edu (USENET News Group Software) Reply-To: clamen+@CS.CMU.EDU Organization: School of Computer Science, Carnegie Mellon University Lines: 24 I am doing research in the area of type evolution in databases (object-oriented databases in particular) and wish to learn a bit more about how existing systems deal with the problem. I'd much appreciate it if those readers with intimate knowledge of a particular DBMS or OODBMS would drop me a note telling me if and how the system provides support for the evolution of types. By "type evolution", I am referring to the process of redefining an existing type (or schema in database parlance) in a DBMS and provisions for the reformatting of the data representing the instances of that type present in the database prior to the redefinition. I am already familiar with the services provided by ORION and GemStone. [Please don't post your replies to the 'net. I will post a summary if people express an interest.] -- Stewart M. Clamen Internet: clamen@cs.cmu.edu School of Computer Science UUCP: uunet!"clamen@cs.cmu.edu" Carnegie Mellon University Phone: +1 412 268 3620 Pittsburgh, PA 15213-3890, USA Fax: +1 412 268 1793