>
> I know some say your unit tests shouldn't touch the DB but the more full
> stack tests I have, the better I sleep at night :-))
>
Unit tests really should be about testing individual bits of logic. Does a
single method do the desired thing, and not the undesired thing...
Ideally, your data ac
ROMs (I would have to generate all the WHEREs for Jim's
option D anyway, the data I am after is only tiny fraction of the original
db...)
- restore the filtered constraints/triggers
Dave Owens
541-359-2602
TU Corporate Website
<http://t.signauxun
.
Of course, I would love to hear about options D) - Z) as well! Thanks in
advance for your input.
Dave Owens
541-359-2602
TU Corporate Website
<http://t.signauxun.com/link?url=http%3A%2F%2Fwww.teamunify.com%2F__corp__%2F&ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgOCP-IMLDA&
