• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

tearing down in memory database hsqldb

 
Ranch Hand
Posts: 308
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi,

i am using hsqldb memory database to test interaction with database (happy path tests, that some data can be entered and deleted), i do not conceive this as a unit tests merely as a integration test.
for achieving that i need a tear down, so test are isolated. problem is that, tearing down does not work properly with hsqldb in memory database.

hsqldb sets up temporary file like mem.lck, mem.log. i try to delete them in my tearDown() method but it seems that sometimes filesystem is not quick enough to delete resources or file is locked, so for instance mem.lck is still there for the next test case which makes tests break.

has anybody experienced same problem and knows a solution for working with tearing down hsqldb memory database?

thanks for information.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic