Skip to content

Releases: babyfish-ct/jimmer

0.9.56

18 Feb 21:37
Compare
Choose a tag to compare
  • #922, #923, #927, #928

  • Add new selectXXX methods

    Query TypeAdded Methods
    Java Root QueryselectCount
    Java Sub QueryselectCount
    selectString
    selectNumber
    selectComparable
    Kotlin Root QueryselectCount
    Kotlin Sub QueryselectCount

v0.9.55

16 Feb 01:04
Compare
Choose a tag to compare
  1. Merge #920 and fix errors of other test cases
  2. Let generated input DTO can be used by @argument of spring-graphql (work with graphql-java)
  3. Big change of jimmer-examples

v0.9.54

15 Feb 20:02
Compare
Choose a tag to compare

Deeply resolve more problem of #885

In most cases, entities should belong to a separate submodule, not to the Web API module. If the DTO does not override the entity's documentation comments, the Web project will adopt the documentation comments of the entity and its properties across project boundaries to generate OpenAPI and TypeScript code.

3dde79dc5430bc8ff3e552b7915fa5b4

v0.9.52

15 Feb 06:01
Compare
Choose a tag to compare

Fix new problem when provided #918 first time.

v0.9.51

12 Feb 20:05
Compare
Choose a tag to compare

Fix #917 and #919
Provide #918

v0.9.50

10 Feb 19:28
Compare
Choose a tag to compare
  1. Fix #908, #912, #915
  2. Provide #900, #910, #914

v0.9.49(Big Change)

06 Feb 05:59
Compare
Choose a tag to compare
  1. Support join fetch for reference association (one-to-one or many-to-one), and property-level configurations are supported by Output DTO.

    Development has been finished now, so documentation is not ready, short guide here

    9 built-in configurations: !fetchType, !where, !orderBy, !filter, !recursion, !limit, !offset, !batch, !depth

    The Antlr grammar for the AST of newest OutputDTO: https://github.com/babyfish-ct/jimmer/blob/main/project/jimmer-dto-compiler/src/main/antlr/org/babyfish/jimmer/dto/compiler/Dto.g4

  2. Global configuration jimmer.mutation-transaction-required, if it is true, any mutation operations without transaction context will report error.

v0.9.47

19 Jan 19:52
Compare
Choose a tag to compare

v0.9.46-Big Change

15 Jan 21:18
Compare
Choose a tag to compare
  1. Big enhancement, merging conflict table joins becomes smarter

    For conflict table joins with different join type (INNER, LEFT, RIGHT, FULL)

    Conflict table joins with same join type will always be merged

    • If join paths are declared in and predicate, they will be merged

      image

      And predicate support simpler code style, not only where(and(a, b)) is OK, but also more styles such as where(a) where(b), where(a, b)

    • If join paths are declared in or predicate, they will not be merged

      image

    Mechanism: There is a class called JoinTypeMergeScope, the default scope is null (Global default scope), the or predicate creates separated merge scope for each sub predicate, only the join paths in same merge scope can be merged.

    Note, if the function or has only one non-null (dynamic predicate such as "table.name eq? sth" may return null) sub predicate argument, this function will be optimized, no or predicate will be created and the argument will be returned directly so that no merge scope will be created.

  2. FR #878 is supported.

v0.9.45

12 Jan 19:42
Compare
Choose a tag to compare
  1. Enhance UpsertMask
  2. #874, #875, #876