When continue the implementation of #138 and trying to add unique constraints or indexes, we found that hibernate-dialect and/or the sqlite-jdbc quarkus extension is not generating them properly. As I couldn't find a way to properly define them on startup with hibernate that doesn't require application code, at this point we will better use flyway to also explore the usage for the future DB-related output (see #152).
This means that hibernate will only validate if the entities are well-defined, and we can evolve the model with only scripts. At the moment, those scripts would be separated by model and versioned with V0.0.*, but I am not sure if we will reallt need them versioned as the DB is only supposed to be created at runtime at the moment (in-memory, although this might also change in the near future to have a better dev-experience - see also #149 for an option to expose a picocli argument to dump/create the database on disk).
When continue the implementation of #138 and trying to add unique constraints or indexes, we found that hibernate-dialect and/or the sqlite-jdbc quarkus extension is not generating them properly. As I couldn't find a way to properly define them on startup with hibernate that doesn't require application code, at this point we will better use flyway to also explore the usage for the future DB-related output (see #152).
This means that hibernate will only validate if the entities are well-defined, and we can evolve the model with only scripts. At the moment, those scripts would be separated by model and versioned with
V0.0.*, but I am not sure if we will reallt need them versioned as the DB is only supposed to be created at runtime at the moment (in-memory, although this might also change in the near future to have a better dev-experience - see also #149 for an option to expose a picocli argument to dump/create the database on disk).