How to check JPA ER Diagram in IntelliJ

By -
When developing with JPA, there are many times when you want to see the relationship between JPA entities at a glance rather than checking the relationship between the actual tables.
In particular, there is a limit to tracking complex relationships between entities only with code.

In this case, IntelliJ supports JPA Entity-based ER Diagram.
You can check it without any special big settings, so let’s see how to do it right away.

1. Enabling JPA Support for your project
Those who have already activated JPA Support for their project can go directly to #2.

First, go to IntelliJ by clicking File -> Project Structure in the upper left corner.



In the Project Structure pop-up, on the left Project Settings item, select Modules -> Main of the project -> +Click the button at the top .


+If you press the button, you can see various supports as below.
Select JPA here.



If you select JPA, you can select JPA Default Provider in the lower right corner as shown below.
Choose the JPA implementation you use.
In general, Hibernate will be the most likely implementation.

Those using Spring Data JPA can also choose Hibernate.



Now this is the end of the project setup.
Let’s open the ER Diagram right away.

2. Open ER Diagram
If you look at the bottom left of IntelliJ , you can see the Persistence tab.
After selecting the tab , right-click on entityManagerFactory and select ER Diagram.

If the entityManagerFactory is not visible, select any entity in the Persistence tab and right-click to see the ER Diagram selection window.



If you select the ER Diagram in this way, you can check the ER Diagram where the Entity relationship is drawn as shown below.



There are several options at the top of the ER Diagram screen.



These options, in turn, can turn on/off the following settings.

Entity property value on/off
Embeddable Entity on/off
SuperClass Entity on/off
You can view only the area you want to see by selectively activating it.

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more