Geek Answers Handbook

ORM: handwritten diagram or auto-generation?

Should I use a handwritten diagram for my forecast developed in a high-level language (for example, Python, Ruby), or should I allow my ORM solution to automatically generate it? In the end, I will need to migrate without destroying all the data. This is normal to be tied to a specific DBMS, but it would be nice if functions such as restrictions and procedures were somehow supported.

+5
source share
4 answers

I never go with an ORM-generated schema.

I find that the ways in which ORM wants to generate a schema often have a common chance of how I want my database structured. In addition, and I know that this is trivial, the nomenclature scheme is usually bad.

The database structure has its own limitations, which I found that usually the automatic generation of ORM tools are not fully considered. And if you want to run reports in your database later (and you will), it is very important to have a good database structure and design.

+3
source

See this horror coding article and links for a discussion of this migration that you will eventually need to do. Plan it now.

. ; , . , , QA .

+2

ORM . , -. - , ORM , , .

+1

ORM , ; .

0

More articles:


All Articles