Refactoring 중 data modeling을 다시 하다보니 db table을 변경해야할 필요가 생겼음.
기존 table들이 single table inheritance형태로 되어 있던데 적당히 정규화 해서 분리해야할 듯함.
http://stackoverflow.com/a/1568007
Martin Fowler discusses this extensively in his book Patterns of Enterprise Application Architecture book. Get this book and look into:
The Website should give you some idea. You might also want to read the section on inheritance mappers. Each of the different approaches have their pros and cons so choose wisely.
Single Table Inheritance
http://martinfowler.com/eaaCatalog/singleTableInheritance.html
Class Table Inheritance
http://martinfowler.com/eaaCatalog/classTableInheritance.html
Concrete Table Inheritance
http://martinfowler.com/eaaCatalog/concreteTableInheritance.html
How to Model Inheritance in a Relational Database
http://www.vertabelo.com/blog/technical-articles/inheritance-in-a-relational-database
: 관련 article, view를 사용해서 적절한 data structure를 제공해 주는 방법
댓글 없음:
댓글 쓰기