1, primary key same one-to-one relationship (store and merchant account management)
Two entity classes use the same primary key, and conversely, bodies with the same primary key are treated as one-to-one relationships. This saves the foreign Key association.
Store Category:
@Entity @table (name= "Tb_store") Public classStore {@Id @GeneratedValue (strategy=Generationtype.auto)PrivateInteger ID; /*** Detailed store address outside of district information*/@Column (Nullable=false) PrivateString address; /*** Business Name*/@Column (Nullable=false) PrivateString name;}
Merchant Account:
/** * @authorJL User Class*/@Entity//entity class configuration@Table (name = "Tb_seller")//Table Configuration Public classSeller {/*** This is only set as the primary key, but not self-growing. */@IdPrivateInteger ID; @OneToOne @PrimaryKeyJoinColumnPrivateStore store; }
When it was created:
Create a store first, then a new seller, assign the store's ID to seller, and then create the seller
Done