BDTREL.TXT 5.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177
  1. IBM Informix
  2. Release Notes for IBM Informix Binary DataBlade Module
  3. 1.00.UC1, March 22, 2006
  4. =================================
  5. TABLE OF CONTENTS
  6. I. OVERVIEW OF RELEASE NOTES
  7. II. NEW FEATURES
  8. III. IBM INFORMIX DYNAMIC SERVER COMPATIBILITY
  9. IV. REGISTERING THE BINARY DATABLADE MODULE
  10. V. UNREGISTERING THE BINARY DATABLADE MODULE
  11. VI. KNOWN PROBLEMS AND WORKAROUNDS
  12. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  13. I. OVERVIEW OF RELEASE NOTES
  14. =============================
  15. The purpose of these release notes is to make you aware of any special
  16. actions required to register, configure, and use the Binary DataBlade
  17. module on your computer. This file also describes new features and feature
  18. differences from earlier versions of this product and other IBM Informix
  19. products, and how these differences affect current products. In addition,
  20. this file contains information about known bugs and their workarounds.
  21. These release notes are written for the following audience:
  22. o System administrators who install IBM Informix Dynamic Server
  23. and the Binary DataBlade module
  24. o Database administrators who control access to IBM Informix
  25. Dynamic Server databases
  26. o Developers who write applications using the Binary DataBlade
  27. module
  28. II. NEW FEATURES
  29. =================
  30. This is a new datablade that provides an indexable binary datatype to
  31. IBM Informix Dynamic Server. It is similar to the CHAR FOR BIT DATA type
  32. in IBM DB2 Universal Database and Oracle's RAW data type. It is a variable
  33. length opaque type with a maximum length of 255 bytes.
  34. The binaryvar data type takes its input as a series of bytes. The bytes can be
  35. either stored directly in a variable or via its ASCII 2 hexadecimal (0-9,A-F)
  36. digit equivalent. The characters A-F may be represented in either upper case
  37. or lower case. If the ASCII representation is used, an even number of bytes
  38. must be entered, otherwise an error will be generated. It is permissible
  39. to add a leading '0X' prefix to the string, but no spaces or other separators
  40. are supported in the ASCII representation.
  41. Example:
  42. create table bindata_test (int_col integer, bin_col binaryvar)
  43. insert into bindata_test values (1, '30313233343536373839')
  44. insert into bindata_test values (2, '0X30313233343536373839')
  45. This would store the binary string of 0123456789 on disk.
  46. The following IBM Informix Dynamic Server built-in string functions are
  47. supported in this release:
  48. length(), octet_length()
  49. Example:
  50. select length(bin_col) from bindata_test where int_col=1;
  51. (expression)
  52. 10
  53. Index operations
  54. This type has support for indexing via the Btree method in this release.
  55. Nested loop joins are supported, but hash joins between binaryvar columns
  56. are not supported in this release. This also impacts GROUP BY and
  57. COUNT DISTINCT operations on this data type.
  58. Bitwise operations
  59. The following bitwise operations are supported in this release:
  60. AND (bit_and), OR (bit_or), XOR (bit_xor), NOT (bit_complement).
  61. The bit_and, bit_or, and bit_xor functions take 2 binaryvar columns or
  62. expressions as arguments. The bit_complement function takes a single
  63. binaryvar column or expression. If either argument is NULL, a NULL binaryvar
  64. is returned. If the lengths of the two arguments are different, the
  65. operation is performed up to the length of the shorter string.
  66. The data from the longer string is copied into the
  67. result from that point.
  68. Example:
  69. create table bindata_test (int_col integer, bin_col binaryvar)
  70. insert into bindata_test values (1, '00001000');
  71. insert into bindata_test values (2, '00002000');
  72. insert into bindata_test values (3, '00004000');
  73. insert into bindata_test values (4, '023A2DE4');
  74. select bit_or(bin_col, '00004000') from bindata_test where int_col=2;
  75. (expression) 00006000
  76. select bit_and(bit_or(bin_col, '40404040'), '01010200')
  77. from bindata_test where int_col=2;
  78. (expression) 00000000
  79. select bit_complement(bin_col) from bindata_test where int_col=4;
  80. (expression) FDC5D21B
  81. select bit_xor(bin_col,'00004040') from bindata_test where int_col=3;
  82. (expression) 00000040
  83. III. IBM INFORMIX DYNAMIC SERVER COMPATIBILITY
  84. ===============================================
  85. Version 1.00.UC1 of the Binary DataBlade module is compatible with
  86. IBM Informix Dynamic Server Version 9.13.UC3 or later.
  87. IV. REGISTERING THE BINARY DATABLADE MODULE
  88. =================================================
  89. To use the Binary DataBlade module, you must register it using
  90. BladeManager in each database in which it will be used.
  91. See the "BladeManager User's Guide" for instructions on how to register
  92. DataBlade modules.
  93. NOTE: You cannot register the Binary DataBlade module into an ANSI-
  94. compliant database. This is because BladeManager does not currently
  95. support the registration of any DataBlade module into ANSI-compliant
  96. databases.
  97. V. UNREGISTERING THE BINARY DATABLADE MODULE
  98. ==================================================
  99. Unregistration removes the definitions for a DataBlade module's user-
  100. defined data types and routines.
  101. You can unregister a DataBlade module that was previously installed only
  102. if there is no data in your database that uses the definitions defined by
  103. the DataBlade module. This means, for example, that if a table is
  104. currently using the binaryvar or binary18 data type, you will not be able to
  105. unregister the Binary DataBlade module from your database.
  106. Unregistration is only available for modules that were registered with
  107. BladeManager.
  108. Refer to the "BladeManager User's Guide" for instructions on how to
  109. unregister DataBlade modules.
  110. VI. KNOWN PROBLEMS AND WORKAROUNDS
  111. ===================================
  112. There are no known issues with this release.
  113. Contact support: http://www.ibm.com/software/data/informix/ids/support/
  114. (C) Copyright IBM Corp. 2006, 2012