On Fri, Mar 08, 2002 at 09:32:56PM -0800, Ian Kallen wrote: > > DBD::JDBC wants the SQL_BIGINT from DBI sql_types but alas, it's not > there. Is there a plan to remedy this?
It was removed in DBI 1.21. The perldoc DBI::Changes says: Removed the definition of SQL_BIGINT data type constant as the value is inconsistent between standards (ODBC=-5, SQL/CLI=25). > I'm assuming that if I'm not > using DBD::ODBC it should be safe to do > > --- /usr/lib/perl5/site_perl/5.6.1/i386-linux/DBI.pm-orig Fri Mar 8 > 21:27:43 2002 > +++ /usr/lib/perl5/site_perl/5.6.1/i386-linux/DBI.pm Fri Mar 8 > 21:11:06 2002 > @@ -151,6 +151,7 @@ > SQL_WVARCHAR > SQL_WCHAR > SQL_BIT > + SQL_BIGINT > SQL_TINYINT > SQL_LONGVARBINARY > SQL_VARBINARY No, you'd need to do more. > ....the data source I'm dealing with has longs (duh, there's no DBD > driver for it, which is why I'm using jdbc instead of DBI directly), so > I'm presuming I'll need SQL_BIGINT to work with it. DBD::JDBC should probably define SQL_BIGINT itself to match whichever value (-5 or 25) it thinks it should use. Tim.