hibernate
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
hibernate [2020/04/29 14:34] – skipidar | hibernate [2023/07/14 12:42] (current) – [Transactional] skipidar | ||
---|---|---|---|
Line 140: | Line 140: | ||
Results in | Results in | ||
+ | |||
+ | **campuses** | ||
+ | ^dtype^id^object_type^name^ | ||
+ | |ECampusPart|497ffe9a-51bb-4ab4-bc3d-b8923d620703|CampusPart|ViennaSmart City Campus front part| | ||
+ | |||
+ | |||
+ | **campusparts** | ||
+ | ^dtype^id^object_type^name^ | ||
+ | |ECampus|dbadab87-7b6d-4e8b-b2c8-0663d68dfe7b|Campus|ViennaSmart City Campus| | ||
+ | |||
**campus_campuspart** | **campus_campuspart** | ||
- | |campus_id|campuspart_id| | + | ^campus_id^campuspart_id^ |
+ | |497ffe9a-51bb-4ab4-bc3d-b8923d620703|dbadab87-7b6d-4e8b-b2c8-0663d68dfe7b| | ||
Line 148: | Line 159: | ||
== Owning-side - with embedded foreign key == | == Owning-side - with embedded foreign key == | ||
- | The alternative to embed the Foreign key - into the CampusPart table: | + | Omitting the " |
<sxh java> | <sxh java> | ||
Line 165: | Line 176: | ||
**campuses** | **campuses** | ||
- | |dtype|id|object_type|name|campus_id| | + | ^dtype^id^object_type^name^campus_id^ |
|ECampusPart|497ffe9a-51bb-4ab4-bc3d-b8923d620703|CampusPart|ViennaSmart City Campus front part|dbadab87-7b6d-4e8b-b2c8-0663d68dfe7b| | |ECampusPart|497ffe9a-51bb-4ab4-bc3d-b8923d620703|CampusPart|ViennaSmart City Campus front part|dbadab87-7b6d-4e8b-b2c8-0663d68dfe7b| | ||
**campusparts** | **campusparts** | ||
- | |dtype|id|object_type|name| | + | ^dtype^id^object_type^name^ |
|ECampus|dbadab87-7b6d-4e8b-b2c8-0663d68dfe7b|Campus|ViennaSmart City Campus| | |ECampus|dbadab87-7b6d-4e8b-b2c8-0663d68dfe7b|Campus|ViennaSmart City Campus| | ||
Line 198: | Line 209: | ||
+ | ===== Warning: bidirectional relationships ====== | ||
+ | ManyToMany relationships can lead to inconsitancies when | ||
+ | * settings links back | ||
+ | * there are multiple entities linking, back to parents | ||
+ | * entities have inconsistant list of members | ||
+ | {{https:// | ||
+ | |||
+ | |||
+ | |||
+ | ===== Transactional ===== | ||
+ | |||
+ | Seems like when wiring entities, which are affected on both sides - it should happen in 1 transaction. | ||
+ | |||
+ | In Spring boot you need to annotate a method with '' | ||
+ | |||
+ | At a high level, Spring creates proxies for all the classes annotated with @Transactional, | ||
+ | |||
+ | https:// | ||
+ | |||
+ | |||
+ | https:// | ||
+ | |||
+ | <sxh java> | ||
+ | @Service | ||
+ | @Getter | ||
+ | public class EquipmentService { | ||
+ | |||
+ | @Autowired | ||
+ | private EquipmentRepository equipmentRepository; | ||
+ | |||
+ | @Transactional | ||
+ | public void updateEquipmentFeeds(ResourcePK equipmentFeeds, | ||
+ | Assert.isTrue(equipmentFeeds.getPartitionId().equals(equipmentTarget.getPartitionId()), | ||
+ | Equipment e1 = equipmentRepository.findById(equipmentFeeds).get(); | ||
+ | Equipment e2 = equipmentRepository.findById(equipmentTarget).get(); | ||
+ | e1.getFeeds().add(e2); | ||
+ | equipmentRepository.save(e1); | ||
+ | } | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | |||
+ | |||
+ | ==== ManyToMany with composite key to self ==== | ||
+ | |||
+ | <sxh java> | ||
+ | |||
+ | @ManyToMany(fetch = FetchType.EAGER, | ||
+ | @JoinTable(name=" | ||
+ | joinColumns={ | ||
+ | @JoinColumn( | ||
+ | name = " | ||
+ | referencedColumnName = " | ||
+ | @JoinColumn( | ||
+ | name = " | ||
+ | referencedColumnName = " | ||
+ | }) | ||
+ | private Set< | ||
+ | |||
+ | |||
+ | // Associations marked as mappedBy must not define database mappings like @JoinTable or @JoinColumn | ||
+ | @ManyToMany( cascade = CascadeType.ALL, | ||
+ | private Set< | ||
+ | </ |
hibernate.1588170857.txt.gz · Last modified: (external edit)