Currently, if you want to use PostgreSQL with the hibernate-vector dependency, when using DevServices with PostgreSQL database, it starts the service with a standard PostgreSQL database image (so no vector type available).
It would be great that if DevServices detects the hibernate-vector dependency, could start the ankane/pgvector:v0.5.1 container image and execute the following command before executing any Hibernate SQL command:
CREATE EXTENSION IF NOT EXISTS vector;
Of course there are workarounds like using quarkus.datasource.devservices.image-name=ankane/pgvector:v0.5.1 and then create an import.sql file with the SQL command. But would be great that devs can smoothly start using vectors.
Description
Currently, if you want to use PostgreSQL with the
hibernate-vector
dependency, when using DevServices with PostgreSQL database, it starts the service with a standard PostgreSQL database image (so novector
type available).It would be great that if DevServices detects the
hibernate-vector
dependency, could start theankane/pgvector:v0.5.1
container image and execute the following command before executing any Hibernate SQL command:Of course there are workarounds like using
quarkus.datasource.devservices.image-name=ankane/pgvector:v0.5.1
and then create animport.sql
file with the SQL command. But would be great that devs can smoothly start using vectors.Implementation ideas
No response