Skip to content

Commit

Permalink
Applied requested changes of review
Browse files Browse the repository at this point in the history
  • Loading branch information
beikov committed Feb 9, 2018
1 parent 25baa30 commit e962209
Show file tree
Hide file tree
Showing 3 changed files with 25 additions and 10 deletions.
15 changes: 7 additions & 8 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,23 +25,22 @@ Not yet released - [Release tag](https://github.com/Blazebit/blaze-persistence/r
### New features

* Keyset pagination generates more efficient predicates that can make use of indexes more easily
* A very advanced prototype for updatable entity views was introduced. You might want to check out the [documentation](https://persistence.blazebit.com/documentation/entity-view/manual/en_US/index.html#updatable-entity-views)
* A very advanced prototype for Updatable Entity Views was introduced. You might want to check out the [documentation](https://persistence.blazebit.com/documentation/entity-view/manual/en_US/index.html#updatable-entity-views)
* Introduced DeltaSpike Data integration and aligned the Spring Data integration with it
* Introduced Maven archetypes for Java EE, DeltaSpike Data and Spring Boot
* Support for DML operations on entity collections
* Conversion between of entity views to other types
* Conversion between Entity View types
* Support for attribute converters in Entity Views

### Bug fixes

* The cyclic join dependency algorithm wrongly reported an error when entity joins were used
* Wrong interpretation of alias when same named association exists
* Entity type related correlation mapping issue
* Some Entity View inheritance mappings lead to clashing constructors to be generated
* Entity View inheritance for deep(3+ levels) polymorphic entity hierarchies produced wrong results
* Expression copying didn't work properly which lead to wrong queries after some optimizations
* Wrong interpretation of alias when same named association existed
* Some Entity View inheritance mappings led to the generation of clashing constructors
* Entity View inheritance for deep (3+ levels) polymorphic entity hierarchies produced wrong results
* Expression copying did not work properly which led to wrong queries after some optimizations
* Implicit joins on a query that happened in expressions of subqueries were wrongly removed in paginated queries
* Flat view i.e. views for Embeddable types haven't been instantiated if all properties were null
* Flat views were not instantiated if all properties were null

### Backwards-incompatible changes

Expand Down
18 changes: 17 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,22 @@ Blaze-Persistence is split up into different modules. We recommend that you defi
</properties>
```

Alternatively you can also use our BOM in the `dependencyManagement` section.

```xml
<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.blazebit</groupId>
<artifactId>blaze-persistence-bom</artifactId>
<version>1.2.0-Alpha3</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
```

## Quickstart

If you want a sample application with everything setup where you can poke around and try out things, just go with our archetypes!
Expand Down Expand Up @@ -390,7 +406,7 @@ public interface SimpleCatView {
```

The `CatView` has a property `cuteName` which will be computed by the JPQL expression `CONCAT(mother.name, 's kitty ', name)` and a subview for `father`. Note that although not required in this particular case,
every entity view for an Entity type should have an id mapping if possible. Entity views without an id mapping will by default have equals and hashCode implementations that consider all attributes, whereas with an id mapping, only the id is considered.
every entity view for an entity type should have an id mapping if possible. Entity views without an id mapping will by default have equals and hashCode implementations that consider all attributes, whereas with an id mapping, only the id is considered.
The `SimpleCatView` is the projection which is used for the `father` relation and only consists of the `id` and the `name` of the `Cat`.

You just created two DTO interfaces that contain projection information. Now the interesting part is that entity views can be applied on any query, so you can define a base query and then create the projection like this:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Christian Beikov
:linkattrs:

It has been too long since the last official release, almost a year!
But don't think we didn't do anything in this time, as you can imagine, there are many features that have been implemented which are part of this release
But don't think we didn't do anything in this time! Many new and shiny features are part of this release.

* https://github.com/Blazebit/blaze-persistence/issues/328[*#328*, window="_blank"] DeltaSpike Data integration
* https://github.com/Blazebit/blaze-persistence/issues/361[*#361*, window="_blank"] Entity view attribute converter support
Expand Down

0 comments on commit e962209

Please sign in to comment.