Skip to content

Commit 19ae286

Browse files
author
kmsoln
committed
[JPA] Enhance Text.
1 parent b38fd90 commit 19ae286

34 files changed

Lines changed: 36 additions & 102 deletions

‎docs/en/jpa/practice/creation/characteristics.md‎

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -106,9 +106,6 @@ You can repeat the previous steps to create entity characteristics for the `Cour
106106
- `online` (boolean): Indicates if the course is online.
107107
- `startDate` (Date): Start date of the course.
108108

109-
110-
## Conclusion
111-
112-
This guide has outlined the process of defining entity characteristics in a Spring Boot project with JPA. By establishing attributes for tables such as Student, Course, and Enrollment, data integrity and consistency have been ensured. Annotations have been utilized to enforce constraints and behaviors for each attribute, providing a solid foundation for the application's data model. With these entity characteristics defined.
109+
---
113110

114111
# [Next: Managing Relationships](relationships.md)

‎docs/en/jpa/practice/creation/create-entity.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,8 +55,6 @@ The `@Entity` annotation indicates that this class is a JPA entity.
5555

5656
Repeat the above steps to create `Enrollment` and `Course` entity classes.
5757

58-
## Conclusion
59-
60-
You have now created the folder structure for your entities and created your entity classes in your application.
58+
---
6159

6260
# [Next: Entity Characteristics Definition](characteristics.md)

‎docs/en/jpa/practice/creation/fetching.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -44,8 +44,6 @@ private List<Enrollment> enrollments;
4444

4545
We opt for Lazy loading (`FetchType.LAZY`) in this scenario. Since we may not always need to access all enrollments of a course, Lazy loading ensures that enrollments are fetched only when explicitly requested.
4646

47-
## Conclusion
48-
49-
This guide has provided insights into the concepts of Lazy and Eager loading. By understanding the scenarios where each fetching strategy is appropriate and how to implement them in your entities, you are now equipped to optimize data fetching and improve the performance of your application.
47+
---
5048

5149
# [Next: Create Repository](../interacting/repository.md)

‎docs/en/jpa/practice/creation/relationships.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -39,8 +39,6 @@ Similarly, the relationship between the `Enrollment` entity and the `Course` ent
3939
private Course course;
4040
```
4141

42-
## Conclusion
43-
44-
This guide has elucidated the process of defining relationships between entities. By establishing associations between the `Enrollment` entity and its associated entities `Student` and `Course`, you are now equipped to implement and manage entity relationships effectively within your application.
42+
---
4543

4644
# [Next: Fetching Strategies](fetching.md)

‎docs/en/jpa/practice/dependencies/driver.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -94,9 +94,7 @@ implementation 'com.microsoft.sqlserver:mssql-jdbc:9.4.0.jre11'
9494

9595
These dependencies facilitate database connectivity.
9696

97-
## Conclusion
98-
99-
By configuring the appropriate database drivers for various databases, you will be equipped to initiate development on your Spring Boot application with JPA.
97+
---
10098

10199
# [Next: Spring Boot and JPA Dependencies](jpa.md)
102100

‎docs/en/jpa/practice/dependencies/jpa.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,8 +52,6 @@ implementation "org.springframework.boot:spring-boot-starter-data-jpa"
5252

5353
This dependency simplifies the setup of JPA-based repositories and provides default configurations for Hibernate.
5454

55-
## Conclusion
56-
57-
By configuring the appropriate Spring Boot dependencies for JDBC and JPA, you will be equipped to initiate development on your Spring Boot application with JPA support.
55+
---
5856

5957
# [Next: Entity Creation](../creation/create-entity.md)

‎docs/en/jpa/practice/interacting/jpa-repository.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -48,9 +48,7 @@ public interface CourseRepository extends JpaRepository<Course, Long> {
4848
The `@Repository` annotation is a Spring stereotype annotation used to indicate that the decorated class is a repository component in the data access layer. It serves as a marker for any class that fulfills the role of a repository, facilitating the translation of exceptions into Spring's unified exception hierarchy.
4949

5050

51-
## Conclusion
52-
53-
You have now created a repository class for managing the `Course` entity in your application.
51+
---
5452

5553
# [Next: Create Record](jpa-repository/create.md)
5654

‎docs/en/jpa/practice/interacting/jpa-repository/create.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,8 +33,6 @@ The `save(Course course)` method provided by JpaRepository allows us to persist
3333

3434
By invoking this method and passing a `Course` object as a parameter, JpaRepository automatically handles the process of persisting the entity to the database.
3535

36-
## Conclusion
37-
38-
You have now implemented a method within the `CourseRepository` interface using JpaRepository to create records in the `Course` table. This method provides a convenient way to persist data to the database using JpaRepository in your Spring Boot application.
36+
---
3937

4038
# [Next: Read Record](read.md)

‎docs/en/jpa/practice/interacting/jpa-repository/delete.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,6 @@ The `deleteById(UUID id)` method signature follows a convention recognized by Jp
3636

3737
By adhering to this naming convention, JpaRepository automatically generates the appropriate SQL query behind the scenes to delete the desired record from the database. This simplifies the development process by eliminating the need to write explicit SQL delete statements, allowing developers to focus on defining method signatures that reflect the intended data deletion operations.
3838

39-
## Conclusion
40-
41-
You have now implemented a method within the `CourseRepository` interface using JpaRepository to delete records from the `Course` table. This method provides a convenient way to delete data from the database using JpaRepository in your Spring Boot application.
39+
---
4240

4341
# [Next: Custom Query](query.md)

‎docs/en/jpa/practice/interacting/jpa-repository/query.md‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,6 @@ The `@Query` annotation allows us to define custom JPQL (Java Persistence Query
3838

3939
By using `@Query`, we can create complex queries tailored to specific data retrieval needs, providing flexibility and control over the database operations.
4040

41-
## Conclusion
42-
43-
You have now implemented a custom query method within the `CourseRepository` interface using JpaRepository and the `@Query` annotation to retrieve records from the `Course` table based on a specific condition. This method offers a powerful way to execute custom queries in your Spring Boot application, enabling precise data retrieval operations.
41+
---
4442

43+
# [Next: Tasks](../../../lab-work.md)

0 commit comments

Comments
 (0)