Home/ Questions/Q 6236227
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T10:48:54+00:00

For integration tests running against 11 different RBDMS for a database abstraction library, I

  • 0

For integration tests running against 11 different RBDMS for a database abstraction library, I need to frequently reset the schema and/or data. This means, I run plenty of statements for most test-cases.

Schema resets are only needed at the beginning of a test-suite. For example:

DROP VIEW
DROP TABLE
DROP SEQUENCE
DROP PROCEDURE
...

CREATE TABLE
...

Data-resets are only needed for tests that write data. For example:

DROP SEQUENCE
DELETE FROM TABLE ...

CREATE SEQUENCE
INSERT INTO TABLE ...

Read-only tests are quite fast, as they don’t need any resetting. Inutitively, I’d just read a SQL file into memory and execute every statement using this:

// No bind variables, all hard parses
// Bind variables won't help much, though as the "hard-parse-reduction" isn't very big.
stmt = connection.createStatement();
stmt.execute(sql);

On some systems, this is quite slow. Is there any better way to do this with JDBC? Or do I have to accept the fact that this can be slow…?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Partial idea: for faster deletes, many DBMS have a “truncate table” statement.

    Another partial idea: instead of deleting and reinstalling everything at the start of the test, you could just copy the files of an empty database. This will require in-depth knowledge of all 11 DBMS though, and you’ll need to shutdown the processes.

    • 0