BEGIN:VCALENDAR
PRODID:-//hacksw/handcal//NONSGML v1.0//EN
METHOD:PUBLISH
BEGIN:VEVENT
DESCRIPTION:Click for Latest Location Information: http://nosql2016.dataversity.net/sessionPop.cfm?confid=97&proposalid=8664\nMost software developed to work with relational databases, and more recently, with NoSQL databases, uses some type of mapping layer to retrieve and persist data between the application layer and the database. For us, this raised the question of how to define the object model and the database schema together, so that one implied the other, and could be used to generate the software artifacts that bind the application to the database.\nTo achieve this capability we defined a schema for describing an object model, and a set of canonical transformations from the object model to the database model. Then we write the code to support these transformations, i.e. to generate DDL, upgrade scripts and method and procedure signatures along with baseline implementation for basic crud operations. \nIn this session I will explain how this all came to be, how it works, and what benefits have accrued, which will include:\nThe objectives for the model doc processor\nDescribing our meta model\nDescribe the mapping from the model to the physical tables\nShow how the model handles various relationships, such as inheritance and containment\nDiscuss our experience and the benefits that we have obtained from using this strategy
DTSTART:20160421T083000
SUMMARY:Agile Schema Management with Model Doc
DTEND:20160421T091459
LOCATION: See Description
END:VEVENT
END:VCALENDAR