This type of relationships seems like an open one, because a record from either side is related to another on the other side. Let's consider one scenario. Here, we will use the Developer
and Technology
classes. In this scenario, multiple developers can associate with multiple technologies and vice versa.
Here, we will create the tables and classes to work this demo.
Use the following script to create the tables if you are not using hbm2dll=create|update
:
Use the following script to create the developer
table:
CREATE TABLE `developer` ( `id` bigint(20) NOT NULL AUTO_INCREMENT, `name` varchar(255) DEFAULT NULL, PRIMARY KEY (`id`) );
Use the following script to create the technology
table:
CREATE TABLE `technology` ( `id` bigint(20) NOT NULL AUTO_INCREMENT, `expertise` varchar(255) DEFAULT NULL, `language` varchar(255) DEFAULT NULL, PRIMARY KEY (`id`) );
Use the following script to create the developer_technology
table:
CREATE TABLE...