Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
SQL Server 2016 schemaInspector.relationExists(tableName) Error #806
The first start (without javers tables) is executed without problems.
The second start goes wrong, SQL Exception because javers tries to recreate the schema for the table jv_commit (which already exists in the DB)
Going through the code, I found the error in the org.javers.repository.sql.schema.JaversSchemaManager
The method ensureTable does not recognize that in the DB SQL Server the table jv_commit already exists and therefore launches again the CREATE TABLE.
This behavior is not present in version 5.0.0 of Javers (which I'm currently using to get around the problem).
Also I think that the problem is attributable to the polyjdbc library
The version of SQL Server I use is:
Well, as you already know, developing on non-OSS databases is hard for us, as we don't have integration tests for it.
It would be nice to have at least local tests running on Docker and Testcontainers.