2
Vote

Output Metadata For Database Tables Created

description

I suggest that you add a feature to output some kind of metadata document after the completion of a migration that describes the current state of the database. In this way, we could hook that output into the code generation system for the data access layer of our applications. For example, you could have the system automatically output a .EDMX file that creates all the mappings between the database tables and an Entity Framework data model. Then, I could use that .EDMX file to code gen my data access layer and basic CRUD operations.
 
If you don't like .EDMX specifically, any simple XML data structure would do.

comments

sebastian_klose wrote Mar 30, 2010 at 3:57 AM

In general I don't think it makes much sense to apply migrations to a EDMX model cause your model usually is part of the same subversion repository as your migrations. So if you update your local working copy you already retrieve the migrated version of the EDMX model. But I get your point that you don't want to do the database changes at two places. At the moment I don't have a good solution to this, but maybe you could explain your idea a little further.

Best regards
Sebastian Klose

wrote Mar 30, 2010 at 3:57 AM

GraemeHill wrote Jun 28, 2010 at 10:57 PM

I think this it is a very good idea.

wrote Feb 12, 2013 at 11:49 PM