|Tuesday, October 21, 2003|
Source: Vincent Massol Think Tank
Let's imagine you wish to perform unit test for code that calls the database. Let's also imagine that you want to test in integration, i.e. verify that the SQL query does actually goes to the database and returns database data.
The traditional approach is to:
There are several disadvantages to point 2:
One solution that our project team discussed yesterday is about using transaction rollbacks. It would work as follows:
I was suprised to see no mention of this on the articles mentioning database unit testing (http://www.dallaway.com/acad/dbunit.html, http://www.dbunit.org/bestpractices.html). The reason may be that there are some glitches with this technique that make it impossible to use in practice... I'd like to know what you think? Have you done this before?
5:46:52 PM trackback  Articulate 
Source: Ming the Mechanic
If you're trying deliberately to think creatively, to come up with new ideas, having a set of stimulating tricks can help. It is quite possible to stimulate lateral thinking in fairly mechanical ways. Lateral thinking is where, instead of following the usual step-by-step logical paths of thinking, you sort of jump to the side and come up with something entirely unexpected. Ed de Bono is one of the champions of lateral thinking.
2:21:12 PM trackback  Articulate 
Source: Wes' Puzzling Blog
Have you ever edited a result set in Enterprise Manager and wished that there was a way to set a field to null? Your in luck because there is a way.
If you are in the field you want to set null you just hit CTRL-0 and leave the field and magically the field has a null value, of course you can only do this on fields that are actually nullable.
Maybe I'm the only person that didn't know about this but I posted this just incase someone else can benefit from this.[Wes' Puzzling Blog]
8:58:16 AM trackback  Articulate