For general information, please refer to the Oracle TransX Utility Users Guide.

• an executable binary
• a user guide document
• a javadoc
• sample files
• readme(this document)

Bug fixes:
2046673 "PRESERVE SPACE" FEATURE DOESN'T WORK ON JAVA VERSION 1.1.8
2061936 FAILED TO UPDATE WHEN UNIQUE KEY IS DATE TYPE
2105351 DOUBLE QUOTE CAN CAUSE A PARSING EXCEPTION
2109203 RAISES AN ERROR UPDATING WITH ONLY KEY COLUMN(S)
2109211 VALIDATION FAILED IF A PARAMETER IS SHARED BY MULTIPLE QUERIES
2114843 ALLOW SHARING REAL COLUMNS AS PARAMETERS AS WELL
2149186 MISSING BOM/ENCODING DECLARATION ON UNLOADED XML FILES

September 30, 2001

Features made available on this release:

• Global/column level/piece wise handling of whitespace normalization
• Unloading
• Improved intimacy with translation exchange formats

Granularity in normalizing whitespace characters can be controlled using the space attribute. It takes either "default" or "preserve". In the default processing, consecutive whitespace characters such as space, tab and line-breaks are replaced with one space character and leading and trailing whitespaces are trimmed away. If declared otherwise, such processing does not occur and all whitespace characters remain as they are. If this attribute is declared at the root table element, it affects all string data in the whole document. If it is specified at a column element in the columns section, it is applicable to the column of every row. If it is specified on a single piece of data on a col element in the dataset section, it is only effective to the data enclosed in the element. Declaration at the document or column level may be overriden with another instance of the space attribute. Specifying the -w option on the command line is equivalent to have space="preserve" at the root element.

Given a table name along with columns to unload, the -s option can be used to generate an XML document in the predefined XML format. If the database has already data loaded and you are considering changing the way it is loaded, this is an easy way to create data files in XML.

The predefined XML format has been enhanced to allow easier transformation to and from translation exchange formats such as XLIFF, TMX, etc. A number of elements and attributes are defined to be counterparts of the notation in the target format.

July 30, 2001

Changes:

  Constant parameter expression
  Making a query virtual

Making a query virtual

A column with a query can also have a virtual attribute. This is useful when used in conjunction with a stored function call whose parameters are supplied from an XML document. In the example below, because all columns are virtual, no data is transferred during the regular data transfer stage. Instead, the values are transferred by a stored function call.

<?xml version="1.0" ?>
<table name="dual">
 <lookup-key/>
 <columns>
  <column name="domain"  type="string" virtual="yes"/>
  <column name="name"    type="string" virtual="yes"/>
  <column name="text"    type="string" virtual="yes" translate="yes"/>
  <column name="country" type="string" virtual="yes" translate="yes"/>
  <column name="dummy" type="number" virtual="yes">
      <query text="select add_nls(:1, :2, :3, :4) dummy from dual" >
        <parameter id="1" col="domain" />
        <parameter id="2" col="name" />
        <parameter id="3" col="text" />
        <parameter id="4" col="country" />
      </query>
   </column>
 </columns>
 <dataset>
  <row>
    <col name="domain">10000</col>
    <col name="name">10001</col>
    <col name="text" trans-key="10001">Text to be translated</col>
    <col name="country" trans-key="10002">us</col>
  </row>
 </dataset>
</table>

Just as constant values can be specified for columns, parameters can be constant as well. In the example below, a constant expression is used for one of the parameters of the procedure. The effect is that the same value is used for every invocation per row.

<?xml version="1.0" ?>
<table name="dual">
 <lookup-key/>
 <columns>
  <column name="domain" type="string" virtual="yes"/>
  <column name="name" type="string" virtual="yes"/>
  <column name="text" type="string" virtual="yes" translate="yes"/>
  <column name="dummy" type="number" virtual="yes">
      <query text="select add_nls(:1, :2, :3, :4) dummy  from dual" >
        <parameter id="1" col="domain" />
        <parameter id="2" col="name" />
        <parameter id="3" col="text" />
        <parameter id="4" constant="us" translate="yes" trans-key="10002"/>
      </query>
   </column>
 </columns>
 <dataset>
  <row>
    <col name="domain">10000</col>
    <col name="name">10001</col>
    <col name="text" trans-key="10001">Text to be translated</col>
  </row>
  <row>
    <col name="domain">10000</col>
    <col name="name">10002</col>
    <col name="text" trans-key="10002">Text to be translated</col>
  </row>
 </dataset>
</table>