What is the practical aspect of Insight.Database.Schema‘s SchemaGroup? Why and how should i use it?
What is the practical aspect of Insight.Database.Schema ‘s SchemaGroup ? Why and how should
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the practical aspect of Insight.Database.Schema‘s SchemaGroup? Why and how should i use it?
I added some more information on the wiki:
https://github.com/jonwagner/Insight.Database.Schema/wiki/Schema-Groups
A summary:
You can use Schema Groups to install multiple schemas into the same database.
Sometimes you have more than one program or component that needs to install SQL into a database. You may also want to manage their schemas separately (perhaps on a separate release cycle).
For example, you have two components in your application. A user membership library and your application code. They both have their own SQL schema.