Class::DBI::column_type vs. Class::DBI::FromCGI

[prev] [thread] [next] [Date index for 2004/06/20]

--J/dobhs11T7y2rNN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

Class::DBI::FromCGI has the ability to auto untaint, when column_type
returns something it groks.

Unfortunately Class::DBI also defines a "column_type". But it's
depracated.

If i get CDBI::FromCGI to use 'Class::DBI::mysql::column_type' as the
method, it works, but that's just plain silly. I'd much rather have CDBI
not mask off the method call.

Since it's been deprecated since 0.90, I reckon it would still be a
while until it's removed, right? OTOH 2 years is a long time.

I couldn't find documentation for column_type before 0.90, so I assume
it was just a way of declaring inflation, by the smell of it alone.

In any case, the auto-untainting is very suitable for my web app, but
I'm not enjoying it (properly). What should I do?

--=20
 ()  Yuval Kogman <nothingmuch@xxxxxxxx.xxx> 0xEBD27418  perl hacker &
 /\  kung foo master: /me climbs a brick wall with his fingers: neeyah!


--J/dobhs11T7y2rNN
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFA1VEXVCwRwOvSdBgRAnyEAJ0Rwphf6M/g5ijqu5Tus1oK+BfdOwCfQ/IY
DFY12GeP5i/tKL3/VljKMSE=
=hnCL
-----END PGP SIGNATURE-----

--J/dobhs11T7y2rNN--