Skip to content

Conversation

@dbraquart
Copy link
Contributor

@dbraquart dbraquart commented Oct 1, 2025

Signed-off-by: David BRAQUART <[email protected]>
Signed-off-by: David BRAQUART <[email protected]>
Signed-off-by: David BRAQUART <[email protected]>
Signed-off-by: David BRAQUART <[email protected]>
@dbraquart dbraquart force-pushed the dbraquart/refacto-use-a-single-entity-for-tabulars branch from e9ec0c0 to ba7f192 Compare October 2, 2025 14:30
dbraquart and others added 4 commits October 9, 2025 15:52
…-a-single-entity-for-tabulars

# Conflicts:
#	pom.xml
#	src/main/resources/db/changelog/db.changelog-master.yaml
…-a-single-entity-for-tabulars

# Conflicts:
#	pom.xml
…-a-single-entity-for-tabulars

Signed-off-by: Franck LECUYER <[email protected]>

# Conflicts:
#	src/main/java/org/gridsuite/modification/server/repositories/NetworkModificationRepository.java
Signed-off-by: Franck LECUYER <[email protected]>
@Table(name = "tabular_modifications")
public class TabularModificationsEntity extends ModificationEntity {

@OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL, orphanRemoval = true)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is FetchType.LAZY by default ...

@sonarqubecloud
Copy link

@dbraquart dbraquart merged commit 9d3673c into main Oct 21, 2025
4 checks passed
@dbraquart dbraquart deleted the dbraquart/refacto-use-a-single-entity-for-tabulars branch October 21, 2025 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants