Mapping Entity Class Names to SQL Table Names with JPA

Last updated: January 8, 2024

Written by: baeldung

Reviewed by: Rui Vilao

Refactor Java code safely — and automatically — with OpenRewrite.

Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.

Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.

Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.

Regression testing is an important step in the release process, to ensure that new code doesn't break the existing functionality. As the codebase evolves, we want to run these tests frequently to help catch any issues early on.

The best way to ensure these tests run frequently on an automated basis is, of course, to include them in the CI/CD pipeline. This way, the regression tests will execute automatically whenever we commit code to the repository.

In this tutorial, we'll see how to create regression tests using Selenium, and then include them in our pipeline using GitHub Actions:, to be run on the LambdaTest cloud grid:

>> How to Run Selenium Regression Tests With GitHub Actions

1. Introduction

In this short tutorial, we’ll learn how to set SQL table names using JPA.

We’ll cover how JPA generates the default names and how to provide custom ones.

2. Default Table Names

The JPA default table name generation is specific to its implementation.

For instance, in Hibernate the default table name is the name of the class with the first letter capitalized. It’s determined through the ImplicitNamingStrategy contract.

But we can change this behaviour by implementing a PhysicalNamingStrategy interface.

3. Using @Table

The easiest way to set a custom SQL table name is to annotate the entity with @jakarta.persistence.Table and define its name parameter:

@Entity
@Table(name = "ARTICLES")
public class Article {
    // ...
}

We can also store the table name in a static final variable:

@Entity
@Table(name = Article.TABLE_NAME)
public class Article {
    public static final String TABLE_NAME= "ARTICLES";
    // ...
}

4. Overwriting the Table Name in JPQL Queries

By default in JPQL queries, we use the entity class name:

select * from Article

But we can change it by defining the name parameter in the @jakarta.persistence.Entity annotation:

@Entity(name = "MyArticle")

Then we’d change our JPQL query to:

select * from MyArticle

5. Conclusion

In this article, we’ve learned how JPA generates default table names and how to set SQL table names using JPA.

The code backing this article is available on GitHub. Once you're logged in as a Baeldung Pro Member, start learning and coding on the project.

REST with Spring Boot

Learn Spring Security

Learn Spring

Learn Spring Data JPA

View All Spring Courses

Learn JUnit

Learn Maven

Learn Hibernate JPA

Learn Mockito

View All Courses

Full Archive

Baeldung Ebooks

About Baeldung

1. Introduction

2. Default Table Names

3. Using @Table

4. Overwriting the Table Name in JPQL Queries

5. Conclusion