I poured over the database documentation for v13, noting what appears to be a move away from EntityFramework. I noticed that the detail and best practices is rather scant. I have also combed through the Umbraco.Cms.Infrastructure.Migrations namespaces for clues.
I am new to Umbraco, but not new to CMS or ASP.NET. I am working with a semi-deployed environment with serious content and schema already in play and am trying to make sure I don’t munge up what I already have.
I am adding two tables, one lookup, one for captured data. I am familiar with the controller end of this implementation. I am looking for guidance on migration composition.
Is there a guide out there for answering questions related to:
When implementing a custom table, is there a way to implement custom tables in a new database schema (other than SQL Server’s default ‘dbo’?)
When implementing a concrete version of MigrationBase, should this class exist for the purpose of one single table or is it okay to bundle up an entire multi-table creation in this instance?
One of my tables needs to be hydrated with pre-existing look up data. Is there a preferred method? (I know of Execute.Sql( ) and Insert.IntoTable( ).)
I thought I saw a Migration attribute that decorated classes with a version number. Did that get deprecated?
I think I have a good sense of how to integrate this data with custom controllers and views, even when working with uSkinned. Just trying to see if I am going about this the wrong way.
Any help would be appreciated.