Орхан Гасанлы

This version of ChromeDriver only supports Chrome version 89

// сигнатуры методов могут отличаться
takeBook(); // взять книгу
returnBook(); // вернуть книгу

findBook(); // найти книгу
overdueNotification(User reader); // уведомить о времени возврата

Reader implements iReader
Librarian implements iLibrarian
Supplier implements iSupplier
Admin implements iAdministrator

@NotNull(message = "123")
    @NotEmpty(message = "456")
    private String proxy;

Вопрос: Это тупое решение? если да, то как правильно решить данную задачу?

{
  "movies": [
    {
      "name": "Good omens",
      "year": 2019,
      "description": "TV Series",
      "director": {
        "fullName": "Douglas Mackinnon"
      },
      "cast": [
        {
          "fullName": "Michael Sheen",
          "role": "Aziraphale"
        },
        {
          "fullName": "David Tennant",
          "role": "Crowley"
        }
      ]
    }
  ]
}

-----------------------------------com.example.Example.java-----------------------------------


public class Example {

@SerializedName("movies")
@Expose
public List<Movie> movies = null;

}

-----------------------------------com.example.Movie.java-----------------------------------

public class Movie {

@SerializedName("name")
@Expose
public String name;
@SerializedName("year")
@Expose
public Integer year;
@SerializedName("description")
@Expose
public String description;
@SerializedName("director")
@Expose
public Director director;
@SerializedName("cast")
@Expose
public List<Cast> cast = null;

}

-----------------------------------com.example.Director.java-----------------------------------


public class Director {

@SerializedName("fullName")
@Expose
public String fullName;

}
-----------------------------------com.example.Cast.java-----------------------------------

public class Cast {

@SerializedName("fullName")
@Expose
public String fullName;
@SerializedName("role")
@Expose
public String role;

}

@ManyToOne(fetch = FetchType.LAZY, optional = true)
    @JoinColumn(name = "project_id", nullable = false)
    @OnDelete(action = OnDeleteAction.CASCADE)
    @JsonIgnore
    private Project project;

JPA does offer possibility to cascade operations (merge, persist, refresh, remove) to associated entities. Logic is in JPA and does not utilize database cascades.
There is no JPA standard compliant way to do cascades with database cascades.

There is no clean cut means to do this in JPA. The following will get you what you want... You can use CascadeType.DELETE, however this annotation only applies to the objects in the EntityManager, not the database. You want to be sure that ON DELETE CASCADE is added to the database constraint. To verify, you can configure JPA to generate a ddl file. Take a look at the ddl file, you'll notice that ON DELETE CASCADE is not part of the constraint. Add ON DELETE CASCADE to actual SQL in the ddl file, then update your database schema from the ddl. This will fix your problem .