|
1 | 1 | --- |
2 | | -title: Create an application consuming a calculation view using Hibernate on SAP HANA |
3 | | -description: This tutorial shows how to create an application which uses Hibernate on SAP HANA to read data from a calculation view |
| 2 | +title: Create an app consuming calculation view using Hibernate on SAP HANA |
| 3 | +description: Create an application that uses Hibernate on SAP HANA to read data from a calculation view. |
4 | 4 | primary_tag: products>sap-hana |
5 | 5 | tags: [ tutorial>intermediate, topic>java, products>sap-hana, products>sap-hana\,-express-edition ] |
6 | 6 | --- |
@@ -50,7 +50,7 @@ Replace `<Hibernate user>` with your actual Hibernate connection user. If your p |
50 | 50 | [ACCORDION-END] |
51 | 51 |
|
52 | 52 |
|
53 | | -[ACCORDION-BEGIN [Step 2: ](Update the project configuration)] |
| 53 | +[ACCORDION-BEGIN [Step 2: ](Update project configuration)] |
54 | 54 |
|
55 | 55 | Since the calculation view isn't a table that can be managed by Hibernate, Hibernate must be configured to not create the schema on startup. This can be done by setting the value of the property `hibernate.hbm2ddl.auto` to `none`. |
56 | 56 |
|
@@ -93,7 +93,7 @@ Save the `persistence.xml` file. |
93 | 93 |
|
94 | 94 | [ACCORDION-END] |
95 | 95 |
|
96 | | -[ACCORDION-BEGIN [Step 3: ](Create an entity for the calculation view)] |
| 96 | +[ACCORDION-BEGIN [Step 3: ](Create entity for calculation view)] |
97 | 97 |
|
98 | 98 | In order for Hibernate to be able to run queries against the calculation view and to map the data from the calculation view to Java objects, a Java Persistence API (JPA) entity for the calculation view has to be created. The calculation view's output columns will be mapped as the fields of the entity. |
99 | 99 |
|
@@ -161,7 +161,7 @@ Save the class file. |
161 | 161 | [ACCORDION-END] |
162 | 162 |
|
163 | 163 |
|
164 | | -[ACCORDION-BEGIN [Step 4: ](Run a simple query on the calculation view)] |
| 164 | +[ACCORDION-BEGIN [Step 4: ](Run simple query on calculation view)] |
165 | 165 |
|
166 | 166 | Using the entity created in the previous step, we can now run queries against the calculation view. |
167 | 167 |
|
@@ -246,7 +246,7 @@ Found 22472 products |
246 | 246 | [ACCORDION-END] |
247 | 247 |
|
248 | 248 |
|
249 | | -[ACCORDION-BEGIN [Step 5: ](Run a geospatial query on the calculation view)] |
| 249 | +[ACCORDION-BEGIN [Step 5: ](Run geospatial query on the calculation view)] |
250 | 250 |
|
251 | 251 | It's also possible to run more complex queries against a calculation view, for example, geospatial queries leveraging the SAP HANA geospatial engine. |
252 | 252 |
|
@@ -341,7 +341,7 @@ Found 10176 products from Europe |
341 | 341 | [ACCORDION-END] |
342 | 342 |
|
343 | 343 |
|
344 | | -[ACCORDION-BEGIN [Step 6: ]((Optional) Set the calculation view schema as the default schema)] |
| 344 | +[ACCORDION-BEGIN [Step 6 (optional): ](Set calculation view schema as default)] |
345 | 345 |
|
346 | 346 | For flexibility or maintainability reasons it might be preferrable to not have the calculation view schema hard-coded on each entity. |
347 | 347 |
|
|
0 commit comments