Скачать или смотреть How to Map Views with Hibernate Without Generating Tables in Spring Boot

Discover how to effectively map views using Hibernate and JPA in Spring Boot, avoiding unwanted table generation. Learn the best practices and configuration settings needed to streamline your development process.
---
This video is based on the question https://stackoverflow.com/q/75721665/ asked by the user 'davidvera' ( https://stackoverflow.com/u/8521515/ ) and on the answer https://stackoverflow.com/a/75722426/ provided by the user 'davidvera' ( https://stackoverflow.com/u/8521515/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Mapping views with hibernate but avoid table generation in springboot

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Map Views with Hibernate Without Generating Tables in Spring Boot

Mapping views in Hibernate can be a tricky endeavor, especially if you're looking to utilize JPA for querying without inadvertently creating tables for your mapped views. In this guide, we will address this common issue faced by developers and provide a step-by-step guide to achieving a clean mapping setup in Spring Boot.

The Problem

When working with views in Hibernate, a common scenario arises—your views are generated as tables instead of being treated merely as mappings. This can lead to issues where the database schema becomes cluttered with unwanted tables corresponding to your views, which should instead be defined properly in an SQL initialization script.

Example View Class

Consider the following example of a view mapped using Hibernate:

[[See Video to Reveal this Text or Code Snippet]]

Current Configuration

Your application configuration may look something like this:

[[See Video to Reveal this Text or Code Snippet]]

The issue here is that when you run your Spring Boot application, Hibernate generates entities and the related tables in the database, including your views.

The Solution

Step 1: Configure Entity Scanning

One effective way to avoid the generation of tables for your views is to specify a base package for your entity scanning using the @ EntityScan annotation. By doing so, you can separate the classpath into different packages for entities that require table generation and those that simply map views.

Here’s how you can implement this in your application:

[[See Video to Reveal this Text or Code Snippet]]

In the configuration above, only the entities located in the fr.mycompany.app.entity.table package will be scanned for table generation. Your views, which might reside in a separate package (e.g., fr.mycompany.app.entity.view), will not generate corresponding tables in the database.

Step 2: Initialize Your Views Using SQL

Since you want your views to be available for querying without generating them as tables, you can manage the creation of these views through an SQL initialization script. This means that they should be present in an import.sql file located in your classpath.

Make sure this file includes the SQL statements necessary to define your views. Here's a small example of what your SQL file could look like:

[[See Video to Reveal this Text or Code Snippet]]

Summary

By following these steps, you will successfully configure Hibernate to avoid generating tables for your views. Through proper package separation and initialization scripts, you can keep your database schema clean and manage your query capabilities effectively.

Make sure to define and limit entity scanning to only necessary packages.

Implement initialization scripts to manage view creation and prevent table clutter.

Now you can focus on using JPA to run queries against your views without the hassle of unintentional table creations.

By understanding and implementing these configurations, you can streamline your development work in Spring Boot and Hibernate, ensuring that your mapped views function efficiently without contributing to database bloat.