-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
> I'm mostly settled on DBIstcf_STRICT _not_ being the default. > So 'loosely typed' will be the default and people who want an error > if the type can't be cast safely will need to use StrictlyTyped => 1. > > I'm (slightly) open to persuasion, but that seems to fit the general > philosophy of perl and the DBI better. It also makes transition easier > for anyone who happens to have code that calls bind_column with an SQL type. I'd opine that since we're dealing with databases holding Important Things, the default should be to throw an error and make people flip a switch to get lax mode. A large warning in the upgreade notes should suffice for anyone transitioning. > I'm undecided about the name of the attribute to indicate use of > DBIstcf_DISCARD_PV. MinMemory or DiscardString or ...? > I'm leaning more towards DiscardString => 1 as it directly describes > what it does rather than a side-effect. +1 to DiscardString > o I wouldn't mind someone else looking over the changes as although I > currently maintain DBD::ODBC I do not consider myself a DBI internals of > XS expert. >> Post a diff and I'll review it for you. The code you appended previously >> looks ok. Ditto. > o Although my primary impetus for doing this is I need it in DBD::Oracle > I would plan to do something similar in DBD::ODBC once this stuff is > committed. Does anyone know if there are other databases that have mapping issues with integers and Perlish integers other than Oracle? Just curious, as I only personally know how a handful deal with ints internally. - -- Greg Sabino Mullane g...@turnstep.com End Point Corporation PGP Key: 0x14964AC8 200911271301 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAksQFFkACgkQvJuQZxSWSshf5wCgn8mSxnHM4YaUgn9P2wXaxqSe pvgAoIKvRQTZtxGKeJgs4dVzZAvCp1jg =nQJI -----END PGP SIGNATURE-----
