0

Code First or Database First

Which option is better in terms of performance and flexibility?

19th Sep 2018, 12:10 PM
Sithembiso Goqo
Sithembiso Goqo - avatar
6 odpowiedzi
+ 2
Sorry, cognitive dissonance there between the subject line and the description. Could you please clarify your question?
19th Sep 2018, 1:01 PM
Janning⭐
Janning⭐ - avatar
+ 1
thanks Janning
21st Sep 2018, 7:53 AM
Sithembiso Goqo
Sithembiso Goqo - avatar
+ 1
Happy to help. 🙂
21st Sep 2018, 7:54 AM
Janning⭐
Janning⭐ - avatar
0
Its not difficult to learn both at a time, take younger decision
19th Sep 2018, 1:00 PM
onekpsc
0
what is the better option for entity framework: Code-First or Database-First for performance and flexibility?
20th Sep 2018, 8:57 PM
Sithembiso Goqo
Sithembiso Goqo - avatar
0
Not sure if that adds much clarity, but I will try to provide some sort of opinion... You might be referring to this: https://www.c-sharpcorner.com/blogs/entity-framework-code-first-vs-database-first-approach or this: https://stackoverflow.com/questions/5446316/code-first-vs-model-database-first of which I think the latter provides more insight than the former. Since I would imagine most of us on this platform are (or aspire to be) programmers, we would ultimately be biased toward Code First. In a more broad sense than just C#-MySQL specific issues, most often limitations come in the form of vendors. If they keep changing things, this becomes a moving target. The code must be nimble enough to adapt to these scenarios. Database-first can feel like having the tail wag the dog. On the other hand, it would be silly to ignore festering database issues like a black box if you can do something about them -- the state of the tail is one of the main indicators of how the dog is feeling (sad/excited/healthy).
20th Sep 2018, 11:21 PM
Janning⭐
Janning⭐ - avatar