On Tue, Nov 21, 2006 at 06:50:59AM -0800, Dean Arnold wrote: > Steffen Goeldner wrote: > >Dean Arnold wrote: > > > >>Went looking for the symbol, and didn't find it > >>in PurePerl, but it is in dbi_sql.h, so this needs > >>to be added somewhere between lines 51 and 107 of PurePerl.pm > >>(from DBI-1.53 RC1 pkg): > >> > >>use constant SQL_BIGINT => (-5); > > > >There is a small problem: SQL/CLI introduced SQL_BIGINT (25), > >which conflicts with ODBC's SQL_BIGINT (-5): > > > > <http://www.xray.mpe.mpg.de/mailing-lists/dbi/2002-01/msg00493.html> > > > > From DBI/Changes: > > > > Removed the definition of SQL_BIGINT data type constant as the value is > > inconsistent between standards (ODBC=-5, SQL/CLI=25). > > > > From DBI(DBI.pm: > > > > C<SQL_BIGINT> is (currently) omitted, because SQL/CLI and ODBC provide > > conflicting codes. > > <sigh/>...I now see that DBI.xs doesn't include it in constants(). > (thnx for spotting this). > > So what (if anything) do other drivers do to indicate BIGINT ? > Just indicate SQL_DECIMAL/NUMERIC w/ SCALE =0 and a big PRECISION ? > > Any chance we can just agree to pick the ODBC version, and document > appropriately ? IIRC, that has been the general direction of DBI over > recent years. Does that break anything ?
On Tue, Nov 21, 2006 at 07:23:42AM -0800, Dean Arnold wrote: > > FWIW: I just did a check on JDBC, and it uses -5 (same as ODBC): > > http://java.sun.com/j2se/1.4.2/docs/api/constant-values.html#java.sql.Types.BIGINT I agree. Let's define it using the ODBC/JDBC value and just document the issue. Can you look after that Dean? Tim.
