Allow use of custom image in `bobgen-sql`

[brunoluiz]

If a table contains uuidv7() as a DEFAULT it will not work since the image used on the getPsqlDriver (reference) uses pgvector/pgvector:0.8.0-pg16 (Postgres 16) and fails on migrate. A newer image is available as 0.8.1-pg18-trixie.

Another option would be to allow custom images on the getPsqlDriver as well, so it detaches bob from subsequent postgres releases.

Error logs:

go generate ./...
migrating static/migration/20260131114331_init.down.sql...
migrating static/migration/20260131114331_init.up.sql...
getting psql driver: migrating: migrating static/migration/20260131114331_init.up.sql: pq: function uuidv7() does not exist

[stephenafamo]

I like the idea of allowing custom images.

[brunoluiz]

Since the mechanism around custom images might require some thinking, do you think solely bumping the image is enough? Or there is some due diligence for this? Or is the test suite enough?

[stephenafamo]

It actually shouldn't be too difficult to support custom images. But I'm open to bumping the image in the meantime