Skip to content

Fix incorrect NULL values in TABLE_CATALOG returned by getSchemas() for built-in schemas.#2872

Merged
Ananya2 merged 2 commits into
mainfrom
user/anagarg/issue#2863
Jan 6, 2026
Merged

Fix incorrect NULL values in TABLE_CATALOG returned by getSchemas() for built-in schemas.#2872
Ananya2 merged 2 commits into
mainfrom
user/anagarg/issue#2863

Added test cases to validate that DatabaseMetaData.getSchemas() retur…

efc38f6
Select commit
Loading
Failed to load commit list.
Azure Pipelines / public-mssql-jdbc.windows succeeded Jan 6, 2026 in 47m 17s

Build #20260106.3 had test failures

5 errors / 69 warnings

Details

Tests

  • Failed: 19 (0.07%)
  • Passed: 25,981 (98.76%)
  • Other: 306 (1.16%)
  • Total: 26,306

Annotations

Check failure on line 48189 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.windows

Build log #L48189 

Build failed.

Check failure on line 1536 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.windows

Build log #L1536 

Build failed.

Check failure on line 1971 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.windows

Build log #L1971 

Build failed.

Check failure on line 47913 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.windows

Build log #L47913 

Build failed.

Check failure on line 1 in testGetDBColumn

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.windows

testGetDBColumn 

Unexpected error message occurred!An error occurred during the current command (Done status 0). Transaction (Process ID 164) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Raw output 
org.opentest4j.AssertionFailedError: Unexpected error message occurred!An error occurred during the current command (Done status 0). Transaction (Process ID 164) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
	at com.microsoft.sqlserver.jdbc.databasemetadata.DatabaseMetaDataTest.testGetDBColumn(DatabaseMetaDataTest.java:553)

Check failure on line 1 in testExecuteTwoInsertsRowsAndSelect

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.windows

testExecuteTwoInsertsRowsAndSelect 

There is already an object named 'Trigger' in the database.
Raw output 
com.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named 'Trigger' in the database.
	at com.microsoft.sqlserver.jdbc.unit.statement.StatementTest$TCGenKeys.setup(StatementTest.java:2719)

Check failure on line 1 in testExecuteDelAndSelect

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.windows

testExecuteDelAndSelect 

There is already an object named 'Trigger' in the database.
Raw output 
com.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named 'Trigger' in the database.
	at com.microsoft.sqlserver.jdbc.unit.statement.StatementTest$TCGenKeys.setup(StatementTest.java:2719)

Check failure on line 1 in testExecuteInsertAndSelect

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.windows

testExecuteInsertAndSelect 

There is already an object named 'Trigger' in the database.
Raw output 
com.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named 'Trigger' in the database.
	at com.microsoft.sqlserver.jdbc.unit.statement.StatementTest$TCGenKeys.setup(StatementTest.java:2719)
View more details on Azure Pipelines