Geek asks and answers

Best approach for changing the database schema?

I know about various methods (but not knowledge). Like a code generator, ORM, etc., I want to know which one is best when during the development period you can change the database schema (big changes), for example add a column to a table, add a table to the database, change the type column etc. I am currently working on a project in this scheme, changing every day. I use the manual process to create BLL, BOL and DAL, but I have to deal with the problem of managing these layers after changing the database schema. Please tell me how to do this easily?

  • In what technique should I use a code generator, ORM, manual approach, or whatever?
  • performance is also good.
+3
source share
4 answers

This is not about programming, but about project management. Management / client should understand that changing the data schema will often have a very big impact on development time. It doesn’t matter what technology you use, because even with a good code generation tool, you can get 4 hours a day by fixing broken code, skipping properties, new properties, different objects, etc. Make sure you show the time spent on this activity. Show it regularly. As soon as management sees that with 20MD you spend 10MD on changing the level of data access (= no added value for 10MD), they will do something about it.

From a technological point of view, you can use everything that the classes generate for you:

  • Linq to SQL
  • EF with EDMX
  • EF EF Power Tools CTP1

NHibernate, .

Edit:

ASP.NET MVC.

+3

, .

ORM , DAL.

- mygeneration .

, .

, .

+2

, . . . AtomWeaver, EMF Xtext.

IDA AtomWeaver ABSE. ( "", "", "" ..). "" , BLL, BOL DAL. , , .

For databases, there are no predefined code generators, which means that you will need to provide all the necessary code for the generating templates, but at least you will get 100% "your code". Since you already do this manually, you can use this code to “feed” generator templates.

Building code generators take some time. At first, this does not pay off, but as soon as you start to change and can quickly get a new code, you will probably change your mind.

+1
source

ADO.NET Entity Framework is a good one.

0
source

More articles:


All Articles