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



Tim,

I did not know that I was on the dbi-users@xxxxxxxx distribution list, but I must be because I got this message.

My email addresses all appear in the signature block at the end of this message, in case you want to contact me privately.

I am still the maintainer of the SQL Registry, such as it is. There have been very, very few changes to the Registry in several years, which suggests to me that (almost) everybody who needs to register some SQL-related value and is aware of the Registry's existence has probably already done it.

For your convenience, I will send you a copy of the Registry by separate message (I don't want to clutter everybody's In box with the file unless they actively want it).

Hope this helps,
Jim

P.S., The reason that the SQL standards archives no longer accept anonymous FTP is for security reasons. Our work is, of course, not secret, and anybody interested in participating is more than welcome to do so. But, before we put the password protection, the server was hacked and was being used to store and distribute pirated software!

At 4/23/2007 03:37 PM, Tim Bunce wrote:
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.

========================================================================
Jim Melton --- Editor of ISO/IEC 9075-* (SQL) Phone: +1.801.942.0144
Co-Chair, W3C XML Query WG; F&O (etc.) editor Fax : +1.801.942.3345
Oracle Corporation Oracle Email: jim dot melton at oracle dot com
1930 Viscounti Drive Standards email: jim dot melton at acm dot org
Sandy, UT 84093-1063 USA Personal email: jim at melton dot name
========================================================================
= Facts are facts. But any opinions expressed are the opinions =
= only of myself and may or may not reflect the opinions of anybody =
= else with whom I may or may not have discussed the issues at hand. =
========================================================================

.



Relevant Pages

  • "Registry of values" for ANSI X3.135 and ISO/IEC 9075 SQL Standards
    ... 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, ... any more and I'd like to get a copy of the current registry. ...
    (perl.dbi.users)
  • 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: What Linux can learn from Windows...
    ... >>registry was great (mostly, since some of the applications still didn't ... All the configuration everywhere could be ... >>their settings (assuming they followed the standards). ... In Linux, there are many different standards for this with may ...
    (alt.os.linux)
  • Re: WMI usability
    ... The WMI properties are there, ... I don't know if the registry is the only alternative but I ... There is no standard for serial numbers, so WMI depends on manufacturers for ... Enterprise Management and/or Common Information Model standards ...
    (microsoft.public.win32.programmer.wmi)
  • Re: answer this question
    ... As XML in the manifest ... As a Type Library (.tlb) file ... In the Registry ... the sections of the C standards that mention these, ...
    (comp.lang.c)