Introduce a new DatabaseInitializationMode correspond to AutoConfigureTestDatabase.Replace.NON_TEST

[quaff]

We should introduce a new mode which include EMBEDDED and test databases, and make it as default mode.

[wilkinsona]

It would feel a little odd to have a NON_TEST-like value that is used in main code. What would be the benefit?

[quaff]

Users would expect schema initialization for test or demo project that running database in container via testcontainers or docker compose.

[wilkinsona]

I'm not sure that they would. We see the use of Testcontainers or Docker Compose as a way of running/testing your app in a more production-like way. In such a situation, the expectation is that schema initialisation is handled just as it is in production. For that case, the proposed change would be a breaking one as it would become necessary to change configuration otherwise two attempts would be made to initialise the schema.

I think the current distinction between embedded and non-embedded databases is the better one here as it feels consistent with our position of Testcontainers and Docker Compose. As such, I am against changing the default.

Setting reservations about a NON_TEST-like value in main code aside for now, we could consider introducing a new value that you choose to set but I'm not sure it's something that we've seen much need for. This is the first such request that I can recall. Let's see what the rest of the team thinks.