![]() If we want to use Table Per Class Hierarchy in Hibernate applications then we have to use the following steps. In this mechanism, when we store any sub class object then data must be stored in single table in the respective columns, if data is not available for any column then null values will be stored in the respective columns. In Table Per Class hierarchy, we will prepare a table with the columns representing all the properties of the classes which are existed in inheritance. In the above context, to improve data persistency in enterprise applications we have to use ORM implementation, Hibernate is one of the ORM implementation, it has provided the following three strategies to resolve inheritance mismatch. In both the above cases, approaches are different to achieve inheritance kind of feature, it will provide Sub types mismatches between data models, it will reduce data persistency in enterprise applications. In Relational data Model, we will use different approaches to manage inheritance kind of features at databases like maintaining all the classes properties in a single table or defining a separate table for each and every class and providing PK-FK relation between these tables. In Object Oriented Data Model, we will provide inheritance relation between entities in order to improve code Reusability. In general, Front-End applications are able to use Object Oriented Data Model to represent data and Back-End Systems are able to use Relational Data Model to represent data. ![]() In Enterprise Applications, we are able to use the data models like Object Oriented Data Model, Relational Data Model, etc. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |