SQLite is implemented in C, HSQL is implemented in Java. It should be more seamless and easy to integrate SQLite with an application project written in C or C++, whereas I would expect the HSQL technology is easier to integrate with a project written in Java. No doubt there are numerous other more subtle differences … Read more
The ANSI SQL92 standard for querying database metadata is contained within the INFORMATION_SCHEMA data structures. I have no idea whether your database supports this or not, but try the following: SELECT * FROM INFORMATION_SCHEMA.TABLES On further research, it appears that HSQLDB does support INFORMATION_SCHEMA, but with slightly non-standard naming. All of the tables have SYSTEM_* … Read more
Since you are using Hibernate, you could use the property hibernate.hbm2ddl.auto to create the database on startup every time. You would also need to force the spring context to be reloaded after each test. You can do this with the @DirtiesContext annotation. This might add a bit extra overhead to your tests, so the other … Read more
In your unit test or in the @Before / setUp() method, you can add the following line to launch the HSQL Database Manager: org.hsqldb.util.DatabaseManager.main(new String[] { “–url”, “jdbc:hsqldb:mem:testdb”, “–noexit” }); or for the improved Swing version with “more refinements” (but about same functionality) org.hsqldb.util.DatabaseManagerSwing.main(new String[] { “–url”, “jdbc:hsqldb:mem:testdb”, “–noexit” }); The DB manager lets you … Read more
You can ignore these errors. Combination of create-drop and empty (which is the case always for in-memory) database produces these for every database object it tries to drop. Reason being that there is not any database objects to remove – DROP statements are executed against empty database. Also with normal permanent database such a errors … Read more
As said by a previous response there is many possible causes. One of them is that the table isn’t created because of syntax incompatibility. If specific DB vendor syntax or specific capability is used, HSQLDB will not recognize it. Then while the creation code is executed you could see that the table is not created … Read more
You can clear the data by dropping the schema. The default schema is called PUBLIC. If you execute the SQL satement below, it will clear all data and drop all tables. DROP SCHEMA PUBLIC CASCADE Alternatively, if you need the table and schema object definitions, you can create a file: database containing the objects but … Read more
HSQL has built-in GUI query tool called Database manager. In the directory of the database files run: java -cp ../lib/hsqldb.jar org.hsqldb.util.DatabaseManager and then setting the config to: jdbc:hsqldb:file:databaseName Allowed me to edit what I needed in a really convenient way.
Use @DirtiesContext to force a reset. For example I have: @ContextConfiguration(classes={BlahTestConfig.class}) @DirtiesContext(classMode = ClassMode.AFTER_EACH_TEST_METHOD) public class SomeTest { @Autowired XXXX xx; @Autowired YYYY yy; @Before public void setUp() { MockitoAnnotations.initMocks(this); when(YYYY.newYY()).thenReturn(zz); } @Test public void testSomeTest() { XX.changeSomething(“StringTest”); XX.doSomething(); check_for_effects(); } @Test public void testSomeOtherTest() { XX.changeSomething(“SomeotherString”); XX.doSomething(); check_for_effects(); } From spring docs DirtiesContext Indicates … Read more
The two queries express the same question. Apparently the query optimizer chooses two different execution plans. My guess would be that the distinct approach is executed like: Copy all business_key values to a temporary table Sort the temporary table Scan the temporary table, returning each item that is different from the one before it The … Read more