"Registry of values" for ANSI X3.135 and ISO/IEC 9075 SQL Standards



I wonder if someone can help me with this...

In the DBI docs it refers to the range of values that are officially
registered for use by the Perl DBI in the International Standards:

=item C<TYPE> (array-ref, read-only)

Returns a reference to an array of integer values for each
column. The value indicates the data type of the corresponding column.

The values correspond to the international standards (ANSI X3.135
and ISO/IEC 9075) which, in general terms, means ODBC. Driver-specific
types that don't exactly match standard types should generally return
the same values as an ODBC driver supplied by the makers of the
database. That might include private type numbers in ranges the vendor
has officially registered with the ISO working group:

ftp://sqlstandards.org/SC32/SQL_Registry/

Where there's no vendor-supplied ODBC driver to be compatible with,
the DBI driver can use type numbers in the range that is now
officially reserved for use by the DBI: -9999 to -9000.

All possible values for C<TYPE> should have at least one entry in the
output of the C<type_info_all> method (see L</type_info_all>).

=cut

The sqlstandards.org ftp server isn't accepting anonymous ftp access
any more and I'd like to get a copy of the current registry.

Doesn't anyone know where I could get a copy?

Or alternatively, could someone send me Jim Melton's current email address?
(He was the maintainer of the Registry back in 1998. He worked at
Sybase at the time and later at Oracle.)

Tim.
.



Relevant Pages

  • Re: "Registry of values" for ANSI X3.135 and ISO/IEC 9075 SQL Standards
    ... I will send you a copy of the Registry by ... In the DBI docs it refers to the range of values that are officially ... The values correspond to the international standards (ANSI X3.135 ... Where there's no vendor-supplied ODBC driver to be compatible with, ...
    (perl.dbi.users)
  • Re: "Registry of values" for ANSI X3.135 and ISO/IEC 9075 SQL Standards
    ... There have been very, very few changes to the Registry in several years, which suggests to me that everybody who needs to register some SQL-related value and is aware of the Registry's existence has probably already done it. ... The reason that the SQL standards archives no longer accept anonymous FTP is for security reasons. ... In the DBI docs it refers to the range of values that are officially ... Where there's no vendor-supplied ODBC driver to be compatible with, ...
    (perl.dbi.users)
  • Re: truncated data after INSERT with undef in DBI - bug?
    ... All your versions are lower than mine except for the SQL Server ... ODBC driver. ... >> With DBI and SQL Server ODBC driver I have prepared an INSERT statement ... > also want to trace the SQL server using the SQL Profiler tool. ...
    (comp.lang.perl.misc)
  • RE: [ODBC Text Driver] Cannot update. Database or object is read only.
    ... track of the data type/source. ... The text ODBC driver gives the same error, ... > registry (DisabledExtensions and Extensions) ...
    (microsoft.public.access.externaldata)
  • Re: VFP 9 ODBC Not Installing on Win2003 SP1
    ... There is no ODBC driver for VFP9. ... > install on a recent Windows 2003 SP1 install? ... > doesn't deploy any of the dll or settings in the registry. ...
    (microsoft.public.data.odbc)