Repository navigation
fix(jdbc): return all xerial table types - #90
Merged
Merged
Conversation
magnusp
added a commit
that referenced
this pull request
Oct 22, 2026
Closes #50 Part of #54. ## What changed `LibsqlConnection.getMetaData()` now creates `LibsqlDatabaseMetaData` on first use and returns the same instance for the lifetime of the connection. Separate connections get separate instances. A closed connection still throws. The method Javadoc documents the caching contract. The behavior test `LibsqlConnectionTest#getMetaDataIsCachedPerConnection` pins both halves: repeated calls on one connection return the same object, and another connection returns a different object. ## Contract decision Parity with xerial sqlite-jdbc 3.53.4.0. `SQLiteConnection.getSQLiteDatabaseMetaData()` caches its metadata object in a `meta` field and `getMetaData()` delegates to it, so the same instance is returned per connection. This change matches that behavior. No Hrana or sqld constraint makes parity impossible. ## Evidence Failing before the fix: ``` ./mvnw -q -pl libsql-jdbc -am -Dtest=LibsqlConnectionTest#getMetaDataIsCachedPerConnection -Dsurefire.failIfNoSpecifiedTests=false test ``` ``` [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0 java.lang.AssertionError: Expecting actual: com.github.magnusp.libsql.jdbc.LibsqlDatabaseMetaData@58c34bb3 and: com.github.magnusp.libsql.jdbc.LibsqlDatabaseMetaData@56a4479a to refer to the same object ``` Passing after the fix: ``` ./mvnw -q -pl libsql-jdbc -am -Dtest=LibsqlConnectionTest#getMetaDataIsCachedPerConnection -Dsurefire.failIfNoSpecifiedTests=false test ``` No failures (exit 0). Full module suite after the fix: ``` ./mvnw -pl libsql-jdbc -am test ``` ``` Tests run: 170, Failures: 0, Errors: 0, Skipped: 0 BUILD SUCCESS ``` Formatting: ``` ./mvnw spotless:apply BUILD SUCCESS ``` `libsql-itests` and `libsql-conformance` were not run: the #50 Steering evidence asks for `./mvnw -pl libsql-jdbc -am test` and `./mvnw spotless:apply`, and this change touches no live-sqld or conformance path. ## Deviations None. ## Defect coverage This is defect (4) of the four sequenced defects under #50: `getMetaData` caching. It does not reopen the earlier three defects, which were delivered in #90 (`getTableTypes`), #91 (statement leaks), and #93 (`getIndexInfo` escaping). Files touched: - `libsql-jdbc/src/main/java/com/github/magnusp/libsql/jdbc/LibsqlConnection.java` - `libsql-jdbc/src/test/java/com/github/magnusp/libsql/jdbc/LibsqlConnectionTest.java`
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #50. Covers defect (1), table-types completeness, only. The statement leaks,
getIndexInfotable-name escaping, andgetMetaDatacaching remain for the later PRs under #50.What changed
LibsqlDatabaseMetaData.getTableTypesnow returns all four table types xerial 3.53.4.0 reports:TABLE,VIEW,SYSTEM TABLE, andGLOBAL TEMPORARY.getTableTypesReturnsEveryXerialTableType, which calls the metadata method end to end and asserts the returnedTABLE_TYPEvalues rather than the generated SQL.Contract decision
Parity with xerial 3.53.4.0
JDBC3DatabaseMetaData.getTableTypes(lines 1754-1772). The implementation uses the same four-wayUNIONof constant selects. It does not add anORDER BY, matching xerial, which leaves row order unspecified. No Hrana or sqld limitation required a different shape.Evidence
The new test failed on the pre-fix code:
It passes after the fix:
Regression runs:
The conformance suite does not currently call
getTableTypes; it ran as a regression guard for the surrounding metadata behavior.Deviations
none
Defects covered
getTableTypescompleteness.getIndexInfotable-name escaping.getMetaDatacaching.Out-of-scope defects noticed
The other three defects in #50 are still present and intentionally untouched. I did not find additional defects outside this PR's scope.
Files touched
libsql-jdbc/src/main/java/com/github/magnusp/libsql/jdbc/LibsqlDatabaseMetaData.javalibsql-jdbc/src/test/java/com/github/magnusp/libsql/jdbc/LibsqlDatabaseMetaDataTest.java