Database, tables, views etc. created first then model classes created by the ORM framework after
Database-First
1 of 16
Typically used for new applications against legacy (existing/old) databases
Database-First
2 of 16
Easy to create domain models in code using existing database
Database-First
3 of 16
Any change on database side easily reflected on code model side by updating the .edmx file (as simple as telling VS to refresh/update the file while displaying it)
Database-First
4 of 16
If database is large, maintaining or updating domain models or map file can become difficult
Database-First
5 of 16
Changes to database may break application once models are updated in code without there being obvious reasons why (database design normally sits outside of source control, so change control can be difficult)
Database-First
6 of 16
Model classes are created first, then ORM creates the database automatically from them
Code-First
7 of 16
Often faster development than with Database-First
Code-First
8 of 16
Clean, non-auto regenerated POCOs (plain old class objects)
Code-First
9 of 16
No DB model file (.edmx) to update/maintain/get corrupted
Code-First
10 of 16
Make changes and migrate so all changes are contained in one “realm” (the programming code)
Code-First
11 of 16
Changes can be more easily rolled-back if necessary
Code-First
12 of 16
Can be laborious and complicated to create models for large databases
Code-First
13 of 16
Dealing with some database objects (stored procedures etc.) can make things more difficult than with database-first
Code-First
14 of 16
Changes to the database made directly won’t be reflected in the model/application logic at all and can cause serious problems/undetectable or difficult to detect bugs
Code-First
15 of 16
Migration class files sometimes need amending by programmer as scaffolding uses defaults which may not suit all use-cases.
Code-First
16 of 16
Other cards in this set
Card 2
Front
Typically used for new applications against legacy (existing/old) databases
Back
Database-First
Card 3
Front
Easy to create domain models in code using existing database
Back
Card 4
Front
Any change on database side easily reflected on code model side by updating the .edmx file (as simple as telling VS to refresh/update the file while displaying it)
Back
Card 5
Front
If database is large, maintaining or updating domain models or map file can become difficult
Comments
No comments have yet been made