Does YAGNI apply to database design?

Question

In code, it is usually quite easy to add new classes to provide additional functionality, etc. I have a pretty good understanding of refactoring code, and what is connected with this YAGNI usually makes sense to me.

What I'm not so used to is working with a relational database and updating it after its deployment. I am developing a small pet project that I plan to use Release Early, Release often , and I wonder if I should be given data that will not be used in the initial release, but is on the list of planned features? How easy is it to add tables and customize the circuits around since this is adding new classes? Or should I try to create tables for things that I could use, but do not plan in the near future?

Answer 1

, , YAGNI .

, , . (, , . ).

Answer 2

. , , . , , , , , , . , , - , .

, , , , SQL, , .

Answer 3

, YAGNI , , , ( ) ..

, - , scema, . " " , ( , , DBA).

.

Answer 4

. www.agiledata.org . . . , , , . , , . , .

Answer 5

.

: , .

. , , .

. , . . , , .

, , , .., . , , , .

, , , . , . (6 , 50 ) , . , , .

, , , ? , . , . , . , .

​​ , , - , . , , , . , , , , .

. , .., - .

, , . , , , .

Answer 6

. .., . . , , .

, , /. , , .

, , , "" , , , , .

, .

, YAGNI - .

Answer 7

, . YAGNI , , . , .., .

, . , , , , , - .

Answer 8

. , .

, , . , , - Object Role Modeling, . Visiomodeler. , , , , - ; .

In practice, your rdbms can handle quite a lot of bending if you really like transformation expressions; and it's worth it to do it well.

Note. I believe that SQL avoidance methods, such as LINQ and object-relational models, will just be an obstacle to evolving design. Maybe I'm wrong. There is some reason to hope that the Microsoft Entity Framework will include modeling the role of objects; but I only saw oblique links to this feature.