Grails comes with HSQLDB as it’s in-memory db and it’s not difficult to inspect it, but there’s a simpler way than many realise and it’s built into every Grails installation, bundled in the HSQLDB jar lib. I have found this trick is useful when inspecting DB state during integration test execution. Just add the following [...]
Archive for the ‘database’ Category
Categories
- agile (13)
- development (15)
- events (3)
- performance (1)
- technical (22)
- android (1)
- database (1)
- grails (12)
- groovy (2)
- information visualisation (3)
- java (2)
- javascript (4)
- linux (2)
- ops (1)
- os (1)
- testing (13)
- functional tests (2)
- performance testing (3)
- tdd (6)
- uncategorized (3)
- user experience (4)
Search
- 10/GUI: Multitouch to lust for
- Google Chrome Frame
- Selenium has evolved; enter Bromine
- JSON Webtests with Grails
- Evening reading…
- Wolfram Alpha: the promise of divine intelligence?
- No Fluff, Just Stuff 2009. Seattle WA
- Google reader keyboard shortcuts
- Viewing Grails’ in memory HSQLDB
- Respect @ Flickr
- Shan: Great, I wasn't aware of the flash settings. Thanks for the explanation...
- find duplicates: I agree with j pimmel. OFC2 is great but the documentation is very poor for local use. The web site is quite messy too so at one point I ended with u
- Dalton jorge: Hi, Nice tip! I prefer use the DatabaseManager separated from the app, so I do this: 1) in a new terminal, I change dir to the app's path; 2)
About
act:ualise | technical blognotes, observations and obssessions on software quality, agile software development, testing and grails
part of the EnergizedWork experiment