pkgsrc/databases/p5-DBD-Mock/distinfo

$NetBSD: distinfo,v 1.2 2011/08/06 20:10:13 adam Exp $

SHA1 (DBD-Mock-1.41.tar.gz) = dd3b00d4dab7e118426aed6a11a7d2bb024b3bbd
RMD160 (DBD-Mock-1.41.tar.gz) = e495fd9cb8c8553cea13762a5b2eaeacf5e10222
Size (DBD-Mock-1.41.tar.gz) = 46206 bytes
Changes 1.41: * Changed incorrect verion number Changes 1.40: * Fixed bug rt44591 second preapre giving an error * Fixed bug rt57981 warnings during clone * Fixed bug rt63191 Synopsis errors * Fixed bug rt66813 Google's group link in the POD 2011-08-06 22:10:13 +02:00			$NetBSD: distinfo,v 1.2 2011/08/06 20:10:13 adam Exp $
Import p5-DBD-Mock version 1.39. Testing with databases can be tricky. If you are developing a system married to a single database then you can make some assumptions about your environment and ask the user to provide relevant connection information. But if you need to test a framework that uses DBI, particularly a framework that uses different types of persistence schemes, then it may be more useful to simply verify what the framework is trying to do -- ensure the right SQL is generated and that the correct parameters are bound. DBD::Mock makes it easy to just modify your configuration (presumably held outside your code) and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql) in your framework. 2009-01-11 14:50:20 +01:00
Changes 1.41: * Changed incorrect verion number Changes 1.40: * Fixed bug rt44591 second preapre giving an error * Fixed bug rt57981 warnings during clone * Fixed bug rt63191 Synopsis errors * Fixed bug rt66813 Google's group link in the POD 2011-08-06 22:10:13 +02:00			`SHA1 (DBD-Mock-1.41.tar.gz) = dd3b00d4dab7e118426aed6a11a7d2bb024b3bbd`
			`RMD160 (DBD-Mock-1.41.tar.gz) = e495fd9cb8c8553cea13762a5b2eaeacf5e10222`
			`Size (DBD-Mock-1.41.tar.gz) = 46206 bytes`