modelmapper | Sample program to learn the basic usage of ModelMapper

Adding converter directly to ModelMapper like this:

The solution is to create a .env file to set the src folder in PYTHONPATH otherwise pytest is unable to find the model package. Also, putting conftest.py inside the src folder doesn't help as suggested by someone.

The out of the box support for nested collections in jOOQ is via SQL/XML or SQL/JSON, depending on what works best in your SQL dialect. The idea is that you nest collections directly in SQL, serialise the results as XML or JSON, and use JAXB (for XML), or Gson or Jackson (for JSON) behind the scenes to map the document into a hierarchy of Java classes. All of this is quite straightforward and automatic, as soon as you have either JAXB, Gson, or Jackson on your classpath.

An example for your data structures:

You can use converters to specify transformations from one type to another. The source and target type can be the same. Use the addConverter() method to add a general converter to the ModelMapper itself (rather than individually to a specific field). You can use it like this:

It's because You didn't specify gradle task to be run:

Since you have all arguments constructor for class CustomData you can do something like this

Instead of doing the very anti-pattern (if you ask me) :

For PostgreSQL you need to use GenerationType.SEQUENCE instead of GenerationType.IDENTITY.

Then:

I doubt that this is related to ddl-auto. You do not really specify what "doesn't work" means exactly, therefore I can only guess.

The problem might be, that you manipulate your entity in your stream cascade with .peek(i -> i.setLogo(decompressZLib(i.getLogo()))). This is probably not what you want. You should decompress the image in the mapping step instead, such that the uncompressed data is not written back to the Courses entity, but rather to CoursesDto.

Edit: Instead decompressing it directly in the controller, you can also do it in the mapper: