pkgsrc/databases/p5-DBIx-Introspector/distinfo

$NetBSD: distinfo,v 1.2 2014/12/07 22:06:49 mef Exp $

SHA1 (DBIx-Introspector-0.001004.tar.gz) = 28afaa8aed818b719edf8fc835574e14e086fb5e
RMD160 (DBIx-Introspector-0.001004.tar.gz) = 1204f4bb77367b000a8edeac27d9e639a6a3b0b8
Size (DBIx-Introspector-0.001004.tar.gz) = 16621 bytes
Update 0.001003 to 0.001004 0.001004 2014-11-30 21:50:34-06:00 America/Chicago - Fix bug that disallowed false values 2014-12-07 23:06:49 +01:00			$NetBSD: distinfo,v 1.2 2014/12/07 22:06:49 mef Exp $
Import DBIx-Introspector-0.001003 as databases/p5-DBIx-Introspector. DBIx::Introspector is a module factored out of the DBIx::Class database detection code. Most code that needs to detect which database it is connected to assumes that there is a one-to-one mapping from database drivers to database engines. Unfortunately reality is rarely that simple. For instance, DBD::ODBC is typically used to connect to SQL Server, but ODBC can be used to connect to PostgreSQL, MySQL, and Oracle. Additionally, while ODBC is the most common way to connect to SQL Server, it is not the only option, as DBD::ADO can also be used. 2014-07-28 02:22:43 +02:00
Update 0.001003 to 0.001004 0.001004 2014-11-30 21:50:34-06:00 America/Chicago - Fix bug that disallowed false values 2014-12-07 23:06:49 +01:00			`SHA1 (DBIx-Introspector-0.001004.tar.gz) = 28afaa8aed818b719edf8fc835574e14e086fb5e`
			`RMD160 (DBIx-Introspector-0.001004.tar.gz) = 1204f4bb77367b000a8edeac27d9e639a6a3b0b8`
			`Size (DBIx-Introspector-0.001004.tar.gz) = 16621 bytes`