2 Using SQL Data Types in Database Applications

Overview of Character Data Types

You can use these SQL data types to store alphanumeric data:

• CHAR and NCHAR data types store fixed-length character literals.

• VARCHAR2 and NVARCHAR2 data types store variable-length character literals.

• NCHAR and NVARCHAR2 data types store Unicode character data only.

• CLOB and NCLOB data types store single-byte and multibyte character strings of up to (4 gigabytes - 1) * (the value obtained from DBMS_LOB.GETCHUNKSIZE).

• The LONG data type stores variable-length character strings containing up to two gigabytes, but with many restrictions. This data type is provided only for backward compatibility with existing applications. In general in new applications, use CLOB and NCLOB data types to store large amounts of character data, and BLOB and BFILE to store large amounts of binary data.

• The LONG RAW data type is similar to the RAW data type, except that it stores raw data with a length up to two gigabytes. The LONG RAW data type is provided only for backward compatibility with existing applications.

Specifying Column Lengths as Bytes or Characters

You can specify the lengths of CHAR and VARCHAR2 columns as either bytes or characters. The lengths of NCHAR and NVARCHAR2 columns are always specified in characters, making them ideal for storing Unicode data, where a character might consist of multiple bytes. This table shows some column length specifications and their meanings:

When using a multibyte database character encoding scheme, consider carefully the space required for tables with character columns. If the database character encoding scheme is single-byte, then the number of bytes and the number of characters in a column is the same. If it is multibyte, however, then there generally is no such correspondence. A character might consist of one or more bytes, depending upon the specific multibyte encoding scheme and whether shift-in/shift-out control codes are present. To avoid overflowing buffers, specify data as NCHAR or NVARCHAR2 if it might use a Unicode encoding that is different from the database character set.

Choosing Between CHAR and VARCHAR2 Data Types

When deciding which data type to use for a column that stores alphanumeric data in a table, consider these points of distinction:

• Space usage

  To store data more efficiently, use the VARCHAR2 data type. The CHAR data type blank-pads and stores trailing blanks up to a fixed column length for all column values, whereas the VARCHAR2 data type does not add extra blanks.

• Comparison semantics

  Use the CHAR data type when you require ANSI compatibility in comparison semantics (when trailing blanks are not important in string comparisons). Use the VARCHAR2 when trailing blanks are important in string comparisons.

• Future compatibility

  The CHAR and VARCHAR2 data types are fully supported. Today, the VARCHAR data type automatically corresponds to the VARCHAR2 data type and is reserved for future use.

When an application interfaces with Oracle Database, there is a character set on the client and server side. Oracle Database uses the NLS_LANGUAGE parameter to automatically convert CHAR, VARCHAR2, and LONG data from the database character set to the character set defined for the user session, if these are different.

Oracle Database SQL Language Reference explains the comparison semantics that Oracle Database uses to compare character data. Because Oracle Database blank-pads values stored in CHAR columns but not in VARCHAR2 columns, a value stored in a VARCHAR2 column can take up less space than the same value in a CHAR column. For this reason, a full table scan on a large table containing VARCHAR2 columns may read fewer data blocks than a full table scan on a table containing the same data stored in CHAR columns. If your application often performs full table scans on large tables containing character data, then you may be able to improve performance by storing data in VARCHAR2 rather than in CHAR columns.

Performance is not the only factor to consider when deciding which data type to use. Oracle Database uses different semantics to compare values of each data type. You might choose one data type over the other if your application is sensitive to the differences between these semantics. For example, if you want Oracle Database to ignore trailing blanks when comparing character values, then you must store these values in CHAR columns.

Using Character Literals in SQL Statements

Many SQL statements, functions, expressions, and conditions require character literals. For information about using character literals in SQL statements, see Oracle Database SQL Language Reference.

Overview of Numeric Data Types

The SQL data types NUMBER, BINARY_FLOAT, and BINARY_DOUBLE store numeric data.

Use the NUMBER data type to store real numbers in a fixed-point or floating-point format. Numbers using this data type are guaranteed to be portable among different Oracle Database platforms, and offer up to 38 decimal digits of precision. You can store positive and negative numbers of magnitude 1 x 10^-130 through 9.99 x10¹²⁵, and 0, in a NUMBER column.

The BINARY_FLOAT and BINARY_DOUBLE data types store floating-point data in the 32-bit IEEE 754 format and the double precision 64-bit IEEE 754 format respectively. Compared to the Oracle Database NUMBER data type, arithmetic operations on floating-point data are usually faster for BINARY_FLOAT and BINARY_DOUBLE. Also, high-precision values require less space when stored as BINARY_FLOAT and BINARY_DOUBLE.

In client interfaces supported by Oracle Database, the native instruction set supplied by the hardware vendor performs arithmetic operations on BINARY_FLOAT and BINARY_DOUBLE data types. The term native floating-point data type includes BINARY_FLOAT and BINARY_DOUBLE data types and all implementations of these types in supported client interfaces.

The floating-point number system is a common way of representing and manipulating numeric values in computer systems. A floating-point number is characterized by these components:

• Binary-valued sign

• Signed exponent

• Significand

• Base

A floating-point value is the signed product of its significand and the base raised to the power of its exponent, as in this formula:

(-1)sign.significand.baseexponent

For example, the number 4.31 is represented as follows:

(-1)0.431.10-2

The components of the preceding representation are as follows:

Floating-Point Number Formats

A floating-point number format specifies how components of a floating-point number are represented. The choice of representation determines the range and precision of the values the format can represent. By definition, the range is the interval bounded by the smallest and the largest values the format can represent and the precision is the number of digits in the significand.

Formats for floating-point values support neither infinite precision nor infinite range. There are a finite number of bits to represent a number and only a finite number of values that a format can represent. A floating-point number that uses more precision than available with a given format is rounded.

A floating-point number can be represented in a binary system, as in the IEEE 754 standard, or in a decimal system, such as Oracle Database NUMBER. The base affects many properties of the format, including how a numeric value is rounded.

For a decimal floating-point number format like Oracle Database NUMBER, rounding is done to the nearest decimal place (for example. 1000, 10, or 0.01). The IEEE 754 formats use a binary format for floating-point values and round numbers to the nearest binary place (for example: 1024, 512, or 1/64).

The native floating-point data types round to the nearest binary place, so they are not satisfactory for applications that require decimal rounding. Use the Oracle Database NUMBER data type for applications in which decimal rounding is required on floating-point data.

Topics:

• Using a Floating-Point Binary Format

• Special Values for Native Floating-Point Formats

(-1)s 2E (b0 b1 b2 ... bp-1)

Comparison Operators for Native Floating-Point Data Types

Oracle Database defines these comparison operators for operations involving floating-point data types:

• Equal to

• Not equal to

• Greater than

• Greater than or equal to

• Less than

• Less than or equal to

• Unordered

Special cases:

• Comparisons ignore the sign of zero (-0 equals, but is not less than, +0).

• In Oracle Database, NaN equals itself. NaN is greater than everything except itself. That is, NaN == NaN and NaN > x, unless x is NaN.

  See Also:

  "Special Values for Native Floating-Point Formats" for more information about comparison results, ordering, and other actions of special values

Arithmetic Operations with Native Floating-Point Data Types

Oracle Database defines operators for these arithmetic operations:

• Multiplication

• Division

• Addition

• Subtraction

• Remainder

• Square root

You can define the mode used to round the result of the operation. Exceptions can be raised when operations are performed. Exceptions can also be disabled.

Formerly, Java required floating-point arithmetic to be exactly reproducible. IEEE 754 does not have this requirement. Therefore, results of operations (including arithmetic operations) can be delivered to a destination that uses a range greater than the range that the operands of the operation use.

You can compute the result of a double-precision multiplication at an extended double-precision destination. When this is done, the result must be rounded as if the destination were single-precision or double-precision. The range of the result, that is, the number of bits used for the exponent, can use the range supported by the wider (extended double-precision) destination. This occurrence may result in a double-rounding error in which the least significant bit of the result is incorrect.

This situation can occur only for double-precision multiplication and division on hardware that implements the IA-32 and IA-64 instruction set architecture. Thus, except for this case, arithmetic for these data types is reproducible across platforms. When the result of a computation is NaN, all platforms produce a value for which IS NAN is true. However, all platforms do not have to use the same bit pattern.

Conversion Functions for Native Floating-Point Data Types

Oracle Database defines functions that convert between floating-point and other formats, including string formats that use decimal precision (precision may be lost during the conversion). For example, you can use these functions:

• TO_BINARY_DOUBLE, which converts float to double, decimal (string) to double, and float or double to integer-valued double

• TO_BINARY_FLOAT, which converts double to float, decimal (string) to float, and float or double to integer-valued float

• TO_CHAR, which converts float or double to decimal (string)

• TO_NUMBER, which converts a float, double, or string to a number

Oracle Database can raise exceptions during conversion. The IEEE 754 specification defines these exceptions:

• Invalid

• Inexact

• Divide by zero

• Underflow

• Overflow

Oracle Database does not raise these exceptions for native floating-point data types. Generally, situations that raise exceptions produce the values described in Table 2-6.

Client Interfaces for Native Floating-Point Data Types

Oracle Database has implemented support for native floating-point data types in these client interfaces:

• SQL

• PL/SQL

• OCI and OCCI

• Pro*C/C++

• JDBC

Topics:

• OCI Native Floating-Point Data Types SQLT_BFLOAT and SQLT_BDOUBLE

• Native Floating-Point Data Types Supported in ADTs

• Pro*C/C++ Support for Native Floating-Point Data Types

Overview of Date and Time Data Types

Oracle Database supports these date and time data types:

• DATE

  Use the DATE data type to store point-in-time values (dates and times) in a table. The DATE data type stores the century, year, month, day, hours, minutes, and seconds.

• TIMESTAMP

  Use the TIMESTAMP data type to store values that are precise to fractional seconds. For example, an application that must decide which of two events occurred first might use TIMESTAMP. An application that specifies the time for a job might use DATE.

• TIMESTAMP WITH TIME ZONE

  Because TIMESTAMP WITH TIME ZONE can also store time zone information, it is particularly suited for recording date information that must be gathered or coordinated across geographic regions.

• TIME STAMP WITH LOCAL TIME ZONE

  Use TIMESTAMP WITH LOCAL TIME ZONE when the time zone is not significant. For example, you might use it in an application that schedules teleconferences, where participants each see the start and end times for their own time zone.

  The TIMESTAMP WITH LOCAL TIME ZONE type is appropriate for two-tier applications in which you want to display dates and times that use the time zone of the client system. It is generally inappropriate in three-tier applications because data displayed in a Web browser is formatted according to the time zone of the Web server, not the time zone of the browser. The Web server is the database client, so its local time is used.

• INTERVAL DAY TO SECOND

  Use the INTERVAL DAY TO SECOND data type to represent the precise difference between two datetime values. For example, you might use this value to set a reminder for a time 36 hours in the future or to record the time between the start and end of a race. To represent long spans of time with high precision, you can use a large value for the days portion.

• INTERVAL YEAR TO MONTH

  Use the INTERVAL YEAR TO MONTH data type to represent the difference between two datetime values, where the only significant portions are the year and the month. For example, you might use this value to set a reminder for a date 18 months in the future, or check whether 6 months have elapsed since a particular date.

Oracle Database stores dates in its own internal format. Date data is stored in fixed-length fields of seven bytes each, corresponding to century, year, month, day, hour, minute, and second.

Displaying Current Date and Time

Use the SQL function SYSDATE to return the system date and time. You can use the FIXED_DATE initialization parameter to set SYSDATE to a constant, which can be useful for testing.

By default, SYSDATE is printed without a BC or AD qualifier. You can add BC to the format string to print the date with the appropriate qualifier, as in Example 2-1.

SELECT TO_CHAR(SYSDATE, 'DD-MON-YYYY BC') NOW FROM DUAL;
 

NOW
-----------------------
18-MAR-2009 AD
 
1 row selected.

For input and output of dates, the standard Oracle Database default date format is DDEMON-RR. The RR datetime format element enables you store 20th century dates in the 21st century by specifying only the last two digits of the year. For example, the format '13-NOV-54' refers to the year 1954 in a query issued between 1950 and 2049, but to the year 2054 in a query issued between 2050 and 2099.

Changing the Default Date Format

Use these techniques to change the default date format:

• To change on an instance-wide basis, use the NLS_DATE_FORMAT parameter.

• To change during a session, use the ALTER SESSION statement.

To enter dates that are not in the current default date format, use the TO_DATE function with a format mask, as in Example 2-2.

SELECT TO_CHAR(TO_DATE('27-OCT-98', 'DD-MON-RR'), 'YYYY') "Year"
FROM DUAL;
 

Year
----
1998
 
1 row selected.

Be careful when using a date format such as DD-MON-YY. The YY indicates the year in the current century. For example, 31-DEC-92 is December 31, 2092, not 1992 as you might expect. To indicate years in any century other than the current one, use a different format mask, such as the default RR.

Changing the Default Time Format

Time is stored in the 24-hour format: HH24:MI:SS

By default, the time in a DATE column is 12:00:00 A.M. (midnight) if no time portion is specified or if the DATE is truncated.

In a time-only entry, the date portion defaults to the first day of the current month. To enter the time portion of a date, use the TO_DATE function with a format mask indicating the time portion, as in Example 2-3.

DROP TABLE birthdays;
CREATE TABLE birthdays (name VARCHAR2(20), day DATE);
INSERT INTO birthdays (name, day)
  VALUES ('ANNIE',
          TO_DATE('13-NOV-92 10:56 A.M.','DD-MON-YY HH:MI A.M.')
         );

Arithmetic Operations with Date and Time Data Types

Oracle Database provides features to help with date arithmetic, so that you need not perform your own calculations on the number of seconds in a day, the number of days in each month, and so on. Some useful features include:

• ADD_MONTHS function, which returns the date plus the specified number of months.

• SYSDATE function, which returns the current date and time set for the operating system on which the database resides.

• SYSTIMESTAMP function, which returns the system date, including fractional seconds and time zone, of the system on which the database resides.

• TRUNC function, which when applied to a DATE value, trims off the time portion so that it represents the very beginning of the day (the stroke of midnight). By truncating two DATE values and comparing them, you can determine whether they refer to the same day. You can also use TRUNC along with a GROUP BY clause to produce daily totals.

• Arithmetic operators such as + and -. For example, SYSDATE-7 refers to 7 days before the current system date.

• INTERVAL data types, which enable you to represent constants when performing date arithmetic rather than performing your own calculations. For example, you can add or subtract INTERVAL constants from DATE values or subtract two DATE values and compare the result to an INTERVAL.

• Comparison operators such as >, <, =, and BETWEEN.

Converting Between Date and Time Types

Oracle Database provides several useful functions that enable you to convert to and from datetime data types. Some useful functions include:

• EXTRACT, which extracts and returns the value of a specified datetime field from a datetime or interval value expression

• NUMTODSINTERVAL, which converts a NUMBER or expression that can be implicitly converted to a NUMBER value to an INTERVAL DAY TO SECOND literal

• NUMTOYMINTERVAL, which converts a NUMBER or expression that can be implicitly converted to a NUMBER value to an INTERVAL YEAR TO MONTH literal

• TO_DATE, which converts character data to a DATE data type

• TO_CHAR, which converts DATE data to character data

• TO_DSINTERVAL, which converts a character string to an INTERVAL DAY TO SECOND value

• TO_TIMESTAMP, which converts character data to a value of TIMESTAMP data type

• TO_TIMESTAMP_TZ, which converts character data to a value of TIMESTAMP WITH TIME ZONE data type

• TO_YMINTERVAL, which converts a character string to an INTERVAL YEAR TO MONTH type

  See Also:

  Oracle Database SQL Language Reference for details about each function

Importing and Exporting Date and Time Types

TIMESTAMP WITH TIME ZONE and TIMESTAMP WITH LOCAL TIME ZONE values are always stored in normalized format, so that you can export, import, and compare them without worrying about time zone offsets. DATE and TIMESTAMP values do not store an associated time zone, and you must adjust them to account for any time zone differences between source and target databases.

Representing Geographic Data

To represent Geographic Information System (GIS) or spatial data in the database, you can use Oracle Spatial features, including the type MDSYS.SDO_GEOMETRY. You can store the data in the database by using either an object-relational or a relational model. You can use a set of PL/SQL packages to query and manipulate the data.

Representing Multimedia Data

Oracle Multimedia enables Oracle Database to store, manage, and retrieve images, audio, video, or other heterogeneous media data in an integrated fashion with other enterprise information. Oracle Multimedia extends Oracle Database reliability, availability, and data management to multimedia content in traditional, Internet, electronic commerce, and media-rich applications.

Whether you store such multimedia data inside the database as BLOB or BFILE values, or store it externally on a Web server or other kind of server, you can use Oracle Multimedia to access the data using either an object-relational or a relational model, and manipulate and query the data using a set of ADTs.

Oracle Multimedia provides the ORDAudio, ORDDoc, ORDImage, ORDImageSignature, ORDVideo, and SI_StillImage ADTs (including methods) for these purposes:

• Extracting metadata and attributes from multimedia data

• Retrieving and managing multimedia data from Oracle Multimedia, Web servers, file systems, and other servers

• Performing manipulation operations on image data

Representing Large Amounts of Data

Oracle Database provides several data types for representing large amounts of data. These data types are grouped under the general category of Large Objects (LOBs). Table 2-7 describes the different LOBs.

An instance of type BLOB, CLOB, or NCLOB can exist as either a persistent LOB instance or a temporary LOB instance. Persistent and temporary instances differ as follows:

• A temporary LOB instance is declared in the scope of your application.

• A persistent LOB instance is created and stored in the database.

Except for declaring, freeing, creating, and committing, operations on persistent and temporary LOB instances are performed the same way.

The RAW and LONG RAW data types store data that is not interpreted by Oracle Database, that is, it is not converted when moving data between different systems. These data types are intended for binary data and byte strings. For example, LONG RAW can store graphics, sound, documents, and arrays of binary data; the interpretation is dependent on the use.

Oracle Net and the Export and Import utilities do not perform character conversion when transmitting RAW or LONG RAW data. When Oracle Database automatically converts RAW or LONG RAW data to and from CHAR data, as is the case when entering RAW data as a literal in an INSERT statement, the database represents the data as one hexadecimal character representing the bit pattern for every four bits of RAW data. For example, one byte of RAW data with bits 11001011 is displayed and entered as CB.

You cannot index LONG RAW data, but you can index RAW data. In earlier releases, the LONG and LONG RAW data types were typically used to store large amounts of data. Use of these types is no longer recommended for development. If your existing application still uses these types, migrate your application to use LOB types. Oracle recommends that you convert LONG RAW columns to binary LOB (BLOB) columns and convert LONG columns to character LOB (CLOB or NCLOB) columns. LOB columns are subject to far fewer restrictions than LONG and LONG RAW columns.

Representing Searchable Text

Rather than writing low-level code to do full-text searches, you can use Oracle Text. It stores the search data in a special kind of index, and lets you query the data with operators and PL/SQL packages. This technology enables you to create your own search engine using data from tables, files, or URLs, and combine the search logic with relational queries. You can also search XML data this way with the XPath notation.

Representing XML

If you have information stored as files in XML format, or to take an ADT and store it as XML, then you can use the XMLType built-in type.

XMLType columns store their data as either CLOB or binary XML. The XMLType constructor can turn an existing object of any data type into an XML object.

When an XML object is inside the database, you can use queries to traverse it (using the XML XPath notation) and extract all or part of its data.

You can also produce XML output from existing relational data and split XML documents across relational tables and columns. You can use these packages to transfer XML data into and out of relational tables:

• DBMS_XMLQUERY, which provides database-to-XMLType functionality

• DBMS_XMLGEN, which converts the results of a SQL query to a canonical XML format

• DBMS_XMLSAVE, which provides XML to database-type functionality

You can use these SQL functions to process XML:

• EXTRACT, which applies a VARCHAR2 XPath string and returns an XMLType instance containing an XML fragment

• SYS_XMLAGG, which aggregates all of the XML documents or fragments represented by an expression and produces a single XML document

• SYS_XMLGEN, which takes an expression that evaluates to a particular row and column of the database, and returns an instance of type XMLType containing an XML document

• UPDATEXML, which takes as arguments an XMLType instance and an XPath-value pair and returns an XMLType instance with the updated value

• XMLAGG, which takes a collection of XML fragments and returns an aggregated XML document

• XMLCOLATTVAL, which creates an XML fragment and then expands the resulting XML so that each XML fragment has the name column with the attribute name

• XMLCONCAT, which takes as input a series of XMLType instances, concatenates the series of elements for each row, and returns the concatenated series

• XMLELEMENT, which takes an element name for identifier, an optional collection of attributes for the element, and arguments that comprise the content of the element

• XMLFOREST, which converts each of its argument parameters to XML, and then returns an XML fragment that is the concatenation of these converted arguments

• XMLSEQUENCE, which either takes as input an XMLType instance and returns a varray of the top-level nodes in the XMLType, or takes as input a REFCURSOR instance, with an optional instance of the XMLFormat object, and returns as an XMLSequence type an XML document for each row of the cursor

  XMLTRANSFORM, which takes as arguments an XMLType instance and an XSL style sheet, applies the style sheet to the instance, and returns an XMLType

Representing Dynamically Typed Data

Some languages allow data types to change at run time or let a program check the type of a variable. For example, C has the union keyword and the void * pointer, and Java has the typeof operator and wrapper types such as Number. In Oracle Database, you can create variables and columns that can hold data of any type and test such data values to determine their underlying representation. For example, you can have a single table column represent a numeric value in one row, a string value in another row, and an object in another row.

You can use the built-in ADT SYS.ANYDATA to represent values of any scalar type or ADT. SYS.ANYDATA has methods that accept scalar values of any type, and turn them back into scalars or objects. Similarly, you can use the built-in ADT SYS.ANYDATASET to represent values of any collection type. To check and manipulate type information, use the DBMS_TYPES package, as in Example 2-4. With OCI, use the OCIType, OCIAnyData, and OCIAnyDataSet interfaces.

CREATE OR REPLACE TYPE employee_type AS
  OBJECT (empno NUMBER, ename VARCHAR2(10));
/
 
DROP TABLE mytab;
CREATE TABLE mytab (id NUMBER, data SYS.ANYDATA);
 
INSERT INTO mytab (id, data)
VALUES (1, SYS.ANYDATA.ConvertNumber(5));
 
INSERT INTO mytab (id, data)
VALUES (2, SYS.ANYDATA.ConvertObject(Employee_type(5555, 'john')));
 
CREATE OR REPLACE PROCEDURE p IS
  CURSOR cur IS SELECT id, data FROM mytab;
  v_id                        mytab.id%TYPE;
  v_data                      mytab.data%TYPE;
  v_type                      SYS.ANYTYPE;
  v_typecode                  PLS_INTEGER;
  v_typename                  VARCHAR2(60);
  v_dummy                     PLS_INTEGER;
  v_n                         NUMBER;
  v_employee                  employee_type;
  non_null_anytype_for_NUMBER exception;
  unknown_typename            exception;
BEGIN
  OPEN cur;
  LOOP
    FETCH cur INTO v_id, v_data;
    EXIT WHEN cur%NOTFOUND;
 
    /* typecode signifies type represented by v_data.
       GetType also produces a value of type SYS.ANYTYPE with methods you
       can call to find precision and scale of a number, length of a
       string, and so on. */
 
       v_typecode := v_data.GetType (v_type /* OUT */);
 
    /* Compare typecode to DBMS_TYPES constants to determine type of data
       and decide how to display it. */
  
    CASE v_typecode
      WHEN DBMS_TYPES.TYPECODE_NUMBER THEN
        IF v_type IS NOT NULL THEN  -- This condition should never happen.
          RAISE non_null_anytype_for_NUMBER;
        END IF;
 
      -- For each type, there is a Get method.
      v_dummy := v_data.GetNUMBER (v_n /* OUT */);
      DBMS_OUTPUT.PUT_LINE
        (TO_CHAR(v_id) || ': NUMBER = ' || TO_CHAR(v_n) );
 
       WHEN DBMS_TYPES.TYPECODE_OBJECT THEN
         v_typename := v_data.GetTypeName();
         IF v_typename NOT IN ('HR.EMPLOYEE_TYPE') THEN
           RAISE unknown_typename;
         END IF;
         v_dummy := v_data.GetObject (v_employee /* OUT */);
         DBMS_OUTPUT.PUT_LINE
           (TO_CHAR(v_id) || ': user-defined type = ' || v_typename ||
            ' ( ' || v_employee.empno || ', ' || v_employee.ename || ' )' );
    END CASE;
  END LOOP;
  CLOSE cur;
EXCEPTION
  WHEN non_null_anytype_for_NUMBER THEN
    RAISE_Application_Error (-20000,
      'Paradox: the return AnyType instance FROM GetType ' ||
      'should be NULL for all but user-defined types');
  WHEN unknown_typename THEN
    RAISE_Application_Error( -20000, 'Unknown user-defined type ' ||
      v_typename || ' - program written to handle only HR.EMPLOYEE_TYPE');
END;
/
 
SELECT t.data.gettypename() AS "Type Name" FROM mytab t;
 

Type Name
--------------------------------------------------------------------------------
SYS.NUMBER
HR.EMPLOYEE_TYPE
 
2 rows selected.

Representing Data with ANSI/ISO, DB2, and SQL/DS Data Types

You can define columns of tables in Oracle Database through ANSI/ISO, DB2, and SQL/DS data types. Oracle Database internally converts such data types to Oracle Database data types.

The ANSI data type conversions are shown in Table 2-8. The ANSI/ISO data types NUMERIC, DECIMAL, and DEC can specify only fixed-point numbers. For these data types, s defaults to 0.

Table 2-9 shows the SQL/DS and DB2 conversions.

The data types TIME, GRAPHIC, VARGRAPHIC, and LONG VARGRAPHIC of IBM products SQL/DS and DB2 have no corresponding Oracle Database data type, and they cannot be used.

Querying the ROWID Pseudocolumn

Each table in Oracle Database has a pseudocolumn named ROWID, which can appear in a query in either the SELECT list or the WHERE clause.

Example 2-5 uses the ROWID pseudocolumn in the SELECT list of a query. The rowids show how the rows of the table are stored.

DROP TABLE t_tab;  -- in case it exists
CREATE TABLE t_tab (col1 ROWID);
 
INSERT INTO t_tab (col1)
SELECT ROWID
FROM employees
WHERE employee_id > 199;
 

SELECT employee_id, rowid
FROM employees
WHERE employee_id > 199;
 

EMPLOYEE_ID ROWID
----------- ------------------
        200 AAAPeSAAFAAAABTAAC
        201 AAAPeSAAFAAAABTAAD
        202 AAAPeSAAFAAAABTAAE
        203 AAAPeSAAFAAAABTAAF
        204 AAAPeSAAFAAAABTAAG
        205 AAAPeSAAFAAAABTAAH
        206 AAAPeSAAFAAAABTAAI
 
7 rows selected.
 

SELECT * FROM t_tab;
 

COL1
------------------
AAAPeSAAFAAAABTAAC
AAAPeSAAFAAAABTAAD
AAAPeSAAFAAAABTAAE
AAAPeSAAFAAAABTAAF
AAAPeSAAFAAAABTAAG
AAAPeSAAFAAAABTAAH
AAAPeSAAFAAAABTAAI
 
7 rows selected.

ROWID Data Type

In tables that are not index-organized, and in foreign tables, the values of the ROWID pseudocolumn have the data type ROWID. The format of this data type is either restricted, extended or external binary.

Topics:

• Restricted ROWID

• Extended ROWID

• External Binary ROWID

struct riddef {
    ub4    ridobjnum; /* data obj#--this field is 
                         unused in restricted ROWIDs */
    ub2    ridfilenum;
    ub1    filler;
    ub4    ridblocknum;
    ub2    ridslotnum;
}

UROWID Data Type

The rows of some tables have addresses that are not physical or permanent or were not generated by Oracle Database. For example, the row addresses of index-organized tables are stored in index leaves, which can move. Oracle Database provides these tables with logical row identifiers, called logical rowids. Rowids of foreign tables, such as DB2 tables accessed through a gateway, are not standard Oracle Database rowids. Oracle Database provides foreign tables with identifiers called foreign rowids.Oracle Database uses universal rowids (urowids) to store the addresses of index-organized and foreign tables. Both types of urowid are stored in the ROWID pseudocolumn, as are the physical rowids of heap-organized tables.Oracle Database creates logical rowids based on the primary key of the table. The logical rowids do not change if the primary key does not change. The ROWID pseudocolumn of an index-organized table has a data type of UROWID. You can access this pseudocolumn as you would access the ROWID pseudocolumn of a heap-organized table (that is, using a SELECT ROWID statement). To store the rowids of an index-organized table, define a column of type UROWID for the table and retrieve the value of the ROWID pseudocolumn into that column.

Data Type Conversion During Assignments

The data type conversion for an assignment succeeds if Oracle Database can convert the data type of the value to be assigned to the data type of the target.

Assume that test_package, its public variable var1, and table1_tab are declared as follows:

CREATE OR REPLACE PACKAGE test_package AS
  var1 CHAR(5);
END;
/
 
DROP TABLE table1_tab;
CREATE TABLE table1_tab (col1 NUMBER);

In the assignment

variable := expression

the data type of expression must be either the same as, or convertible to, the data type of variable. For example, for this assignment, Oracle Database automatically converts zero to the data type of var1, which is CHAR(5):

var1 := 0;

In the statement

INSERT INTO table1_tab (col1) VALUES (expression)

the data type of expression must be either the same as, or convertible to, the data types of col1. For example, for this statement, Oracle Database automatically converts the string '19' to the data type of col1, which is NUMBER:

INSERT INTO table1_tab (col1) VALUES ('19')

In the statement

UPDATE table1_tab SET column = expression

the data type of expression must be either the same as, or convertible to, the data type of column. For example, for this statement, Oracle Database automatically converts the string '30' to the data type of col1, which is NUMBER:

UPDATE table1_tab SET col1 = '30';

In the statement

SELECT column INTO variable FROM table1_tab

the data type of column must be either the same as, or convertible to, the data type of variable. For example, for this statement, Oracle Database automatically converts the value selected from col1, which is 30, to the data type of var1, which is CHAR(5):

SELECT col1 INTO var1 FROM table1_tab WHERE col1 = 30;

Data Type Conversion During Expression Evaluation

For expression evaluation, Oracle Database can automatically perform the same conversions as for assignments. An expression is converted to a type based on its context. For example, operands to arithmetic operators are converted to NUMBER, and operands to string functions are converted to VARCHAR2.

Oracle Database can automatically convert:

• VARCHAR2 or CHAR to NUMBER

• VARCHAR2 or CHAR to DATE

Character to NUMBER conversions succeed only if the character string represents a valid number. Character to DATE conversions succeed only if the character string satisfies the session default format, which is specified by the initialization parameter NLS_DATE_FORMAT.

Some common types of expressions are:

• Simple expressions, such as:

  commission + '500'
  

• Boolean expressions, such as:

  bonus > salary / '10'
  

• Subprogram calls, such as:

  MOD (counter, '2')
  

• WHERE clause conditions, such as:

  WHERE hiredate = TO_DATE('1997-01-01','yyyy-mm-dd')
  

• WHERE clause conditions, such as:

  WHERE rowid = 'AAAAaoAATAAAADAAA'
  

In general, Oracle Database uses the rule for expression evaluation when a data type conversion is needed in places not covered by the rule for assignment conversions.

In assignments of the form:

variable := expression

Oracle Database first evaluates expression using the conversion rules for expressions; expression can be as simple or complex as desired. If it succeeds, then the evaluation of expression results in a single value and data type. Then, Oracle Database tries to assign this value to the target variable using the conversion rules for assignments.