ID Generation
-------------

When working with H2, the database generated the keys when we inserted the rows with JPA.
We made sure that PostgreSQL is doing the same thing.
What datatype was used for this in schema.sql?
Is there anything that catches your eye when looking at the insert statements? Why is this column omitted from the statements?

Answer:

Records
-------

Have a look at the CustomerInput class. This is a record.
Can you think of reasons why 'data transfer objects' are often implemented with records instead of classes?

Answer:

Repository Interfaces
---------------------

Check the package 'repository'. Why is the CustomerRepository an interface and not a class?

Answer:

Repository Implementations
--------------------------

Note that the 'SpringDataJpaCustomerRepository' is annotated with Primary. What happens if there are multiple implementations
of an interface without Primary? Verify this behaviour by moving Primary to a different class and running the tests.
Why are the tests failing now?

Answer:

CustomerTest
------------

Why do the assertions on the join tables in the delete test make use of a JdbcClient? Is it not possible to check this with Spring Data Repositories?

Answer:
