Warehouse Release 3.01.0080
03/14/2005
The features in the 3.01.0080
release
. A problem handling connect errors on
Oracle has been fixed.
In previous releases since 3.00.4400, an
error encountered
while connecting to
an Oracle database could cause an
abort. If the connection was to a remote Oracle
database
the abort would
happen on the server.
. A problem has been fixed when comparing
items of type TIME
to items of ODBC TIME. Previously, this comparison
would generate
compile time error 8118.
. A problem has been fixed with ODBC TIME
conversions. This
problem seems to
only have affected big endian systems.
. A problem has been fixed with adding and
subtracting
dates, times and intervals. In previous releases certain
operations would
produce a result that was incorrect
by one tenth of a second.
. Added TZH and TZM date formats. TZH is the time zone
hour with a leading
sign (+ or -) and a two digit hour.
TZM is the two digit time zone minute. Example:
$NOW PIC "HH24:MI:SS
TZH:TZM" --> "11:28:12
-08:00"
. Added new Oracle date data types to
improve Oracle support:
ORACLE TIMESTAMP WITH TIME ZONE
Same as the existing ORACLE TIMESTAMP,
but contains
time zone
information in addition to the data and
time down to
the nanosecond.
ORACLE TIMESTAMP WITH LOCAL TIME ZONE
Same as the existing ORACLE TIMESTAMP,
but assumes
the local time
zone.
ORACLE INTERVAL YEAR TO MONTH
An interval
containing only year and month.
No
date
arithmetic operations are available.
ORACLE INTERVAL DAY TO SECOND
An interval
containing days down to nanoseconds.
Date arithmetic operations are
available.
**NOTE: Implementation of these data types
is preliminary
and subject to
change.
. Added interpretation of
Oracle FLOAT data type. Warehouse
now accepts ORACLE
FLOAT as a data type and interprets
it as a ORACLE
NUMBER(126,-127). This is consistent
with the
interpretation given by the Oracle database.
. Added support for Eloquence databases on
HP-UX.
The HP-UX distribution that supports
Eloquence
is suffixed with the
letter F, with the current
release named
3.01.0080-F. At a later date the
HP-UX releases -H and -F will be merged but
at
this time the -H
release supports Oracle and the
-F release supports Eloquence.
Since Eloquence supports the TurboIMAGE API, support was
added as a Warehouse
IMAGE database. As far as
Warehouse is concerned,
an Eloquence database is an IMAGE
database so the
database type IMAGE is used to open an
Eloquence database. The syntax for opening
an Eloquence
database is:
OPEN <db-tag> IMAGE <db-name>
PASS=<db-pass> MODE=<mode>
The only change made to Warehouse to support
Eloquence was
to dynamically load
the IMAGE libraries. The IMAGE
libraries are now
dynamically loaded on all platforms
except MPE/iX where they are statically loaded. Three
environment
variables may be set prior to running Warehouse
to facilitate the
dynamic loading of IMAGE (Eloquence)
libraries. They are WHIMAGEHOME that points to the
Eloquence installation directory, WHIMAGEPATH
that points
to the library
directory within the installation
directory, and
WHIMAGELIB that points to the library file
within the
directory. Warehouse should work without
these
setting these
variables in a standard Eloquence
installation. The default values of the variables are:
Environment variable Default value
WHIMAGEHOME /opt/eloquence6/
WHIMAGEPATH lib/pa11_32
WHIMAGELIB libimage3k.sl
**NOTE: Implementation of these variables
is preliminary
and subject to
change.
. Made improvements to Warehouse client
compile performance.
One change causes database table descriptions
to be cached
on the client to
minimize network transactions. The other
change improves
access time to a heavily utilized internal
table.
. Fixed
a problem that caused DataBridger Studio to use
plaintext passwords
for local databases. Studio should now
use encrypted
passwords for local databases as well as
remote databases.
. The COLATTR keyword has been added to the
OPEN statement for
XML
files. Specifying COLATTR causes XML
file attributes
to be interpreted as
columns. Using COLATTR is the only
method of making
attributes accessible using Warehouse.
The syntax to open an XML file is now:
OPEN db-tag XML xml-file-name [MODE=mode]
[CASEID] [NSTRING] [FLATTEN] [COLATTR]
FLATTEN and COLATTR determine what data is
accessible within
an example. Using FLATTEN makes all elements accessible
and COLATTR makes
all attributes accessible as columns.
Here
are some examples with
the XML file below.
Sample XML file called WEATHER.XML:
<?xml
version="1.0"?>
<WEATHERREPORT xmlns="WeatherSchema.xml">
<STATE STATENAME="
<CITY CITYNAME="
<SKIES>Partly
cloudy</SKIES>
<HI>87</HI>
<LOW>65</LOW>
</CITY>
</STATE>
<STATE STATENAME="
<CITY CITYNAME="
<SKIES>Sunny</SKIES>
<HI>98</HI>
<LOW>74</LOW>
</CITY>
</STATE>
</WEATHERREPORT>
Example 1:
Open weather XML with default parameters and only
CITY is available:
OPEN
Tables available:
CITY
Layout of CITY:
SKIES
HI
LOW
Example 2:
Open weather XML with the COLATTR parameter and
only CITY is
available, but the CITYNAME attribute can be
accessed:
OPEN
Tables available:
CITY
Layout of CITY:
SKIES
HI
LOW
CITYNAME
Example 3:
Open weather XML with the FLATTEN parameter and
WEATHERREPORT, STATE and CITY are available
with KEYLINKS
linking them,
however STATENAME and CITYNAME are not
available because
they are attributes within the XML file:
OPEN
Tables available:
WEATHERREPORT
STATE
CITY
Layout of WEATHERREPORT:
WEATHERREPORT_KEYLINK (Parent
Link)
Layout of STATE:
WEATHERREPORT_KEYLINK (Child
Link)
STATE_KEYLINK (Parent Link)
Layout of CITY:
STATE_KEYLINK (Child Link)
SKIES
HI
LOW
Example 4:
Open weather XML with the both the FLATTEN and
COLATTR parameters. This makes WEATHERREPORT, STATE and
CITY are available
with KEYLINKS linking them. STATENAME and
CITYNAME are also available as columns:
OPEN
Tables available:
WEATHERREPORT
STATE
CITY
Layout of WEATHERREPORT:
XMLNS
WEATHERREPORT_KEYLINK (Parent
Link)
Layout of STATE:
WEATHERREPORT_KEYLINK (Child
Link)
STATENAME
STATE_KEYLINK (Parent Link)
Layout of CITY:
STATE_KEYLINK (Child Link)
SKIES
HI
LOW
CITYNAME
Release 3.01.0080 is available now on all supported platforms.