Steffen Goeldner wrote:
>
> Steffen Goeldner wrote:
> >
> > Tim Bunce wrote:
> > >
> > > I'll happily accept a patch that adds the new standard types as well,
> >
> > Attached.
> >
>
> Sorry, I forgot to patch the documentation ...
>
As an alternative to the long list of constansts, we could provide
a shorter (and more generic) statement.
Steffen
*** DBI-1.20.orig/DBI.pm Sat Aug 25 01:33:52 2001
--- DBI-1.20/DBI.pm Thu Nov 08 20:51:27 2001
***************
*** 1603,1619 ****
=head2 DBI Constants
! The following SQL standard type constants can be imported individually
or, by importing the special C<:sql_types> tag, all together:
- SQL_CHAR SQL_NUMERIC SQL_DECIMAL SQL_INTEGER SQL_SMALLINT
- SQL_FLOAT SQL_REAL SQL_DOUBLE SQL_VARCHAR
- SQL_DATE SQL_TIME SQL_TIMESTAMP
- SQL_LONGVARCHAR SQL_BINARY SQL_VARBINARY SQL_LONGVARBINARY
- SQL_BIGINT SQL_TINYINT
- SQL_WCHAR SQL_WVARCHAR SQL_WLONGVARCHAR
- SQL_BIT
SQL_ALL_TYPES
See the L</type_info>, L</type_info_all>, and L</bind_param> methods
for possible uses.
--- 1603,1625 ----
=head2 DBI Constants
! SQL standard type constants can be imported individually
or, by importing the special C<:sql_types> tag, all together:
SQL_ALL_TYPES
+ SQL_CHAR
+ SQL_NUMERIC
+ SQL_DECIMAL
+ ...
+
+ A complete list can easily be obtained:
+
+ use DBI();
+ printf " %-35s%4d\n", $_, $DBI::{$_}() for sort grep /^SQL_/, keys %DBI::
+
+ These constants are defined by SQL/CLI, ODBC or both.
+ C<SQL_BIT> is (currently) omitted, because SQL/CLI and ODBC provide
+ conflicting codes.
See the L</type_info>, L</type_info_all>, and L</bind_param> methods
for possible uses.
