Mimer SQL Documentation TOC PREV NEXT INDEX

Mimer SQL Developer Site


Statements


ALTER IDENT Change Password

The ALTER IDENT USING syntax and the ALTER IDENT IDENTIFIED BY syntax to change password are deprecated and have been replaced by the SET PASSWORD syntax. The old syntax is still supported for backward compatibility.

ALTER STATEMENT

CREATE IDENT AS OS_USER

The possibility to specify OS_USER as ident type is deprecated. The syntax is still supported for backward compatibility.

GET DIAGNOSTICS EXCEPTION INFO

The SQL-2008 standard has adjusted the GET DIAGNOSTICS syntax. The keyword EXCEPTION has been replaced with the keyword CONDITION. As a consequence the exception-clause is now called condition-clause.

The old GET DIAGNOSTICS EXCEPTION INFO syntax is still supported for backward compatibility.

JOIN Without SELECT

The way to write a join without starting with the SELECT keyword has been removed from the SQL standard (SQL-2003 and later). Mimer SQL Engine still supports that construction, but since it is deprecated it may be removed in a future release.

So instead of just writing

 table1 INNER JOIN table2 ON table1.col1 = table2.co2
 

specify the SELECT keyword, like:

 SELECT * FROM table1 INNER JOIN table2 ON table1.col1 = table2.co2

Mimer SQL Experience
The join syntax without starting with SELECT is not supported.

CONNECT

The syntax of the standard CONNECT statement differs from that in earlier versions of Mimer SQL. The previous form is still supported for backward compatibility.

Backward compatibility syntax:



Note: The CONNECT statement and the standard-compliant CONNECT TO statement have different default modes for SET TRANSACTION START. CONNECT uses SET TRANSACTION START EXPLICIT, while CONNECT TO uses SET TRANSACTION START IMPLICIT.

ORDER BY Ordinal Position

Using an integer value to represent the ordinal position in an ORDER BY specification is deprecated due to changes in the SQL standards.

SELECT NULL

The use of the keyword NULL in a select list is still supported for backward compatibility but should be regarded as a deprecated feature in Mimer SQL.

Instead, specify CAST(NULL AS data-type).

Example
 SELECT c1, int_col FROM t1
 UNION
 SELECT c1, CAST(NULL AS integer) FROM t2;

INCLUDE SQLCA

Prior to version 7.2 of Mimer SQL, an INCLUDE SQLCA statement was required in an embedded SQL program, to include the declaration of the SQL communication area.

The INCLUDE SQLCA statement is now no longer required. Instead applications can use the SQLSTATE variable and the GET DIAGNOSTICS statement to get the information that was contained in SQLCA in the earlier Mimer SQL versions.

See Return Status and Conditions for a description of SQLSTATE.

On Windows and Unix/Linux, SQLCA is no longer available. Applications using SQLCA has to be modified to use SQLSTATE or SQLCODE instead.

VMS: For backward compatibility reasons the use of the SQLCA is still supported on VMS.

SET TRANSACTION

Following the introduction of the SET TRANSACTION READ and SET TRANSACTION ISOLATION LEVEL options, the SET TRANSACTION CHANGES options no longer apply.

The following options are supported for backward compatibility only:



CREATE IDENT

The keyword USING is now used when specifying the password-string for the ident being created. The use of IDENTIFIED BY is deprecated.

The following syntax is supported for backward compatibility only:



ENTER

The keyword USING is now used when specifying the password for the program ident being entered. The use of IDENTIFIED BY is deprecated.

The following syntax is supported for backward compatibility only:




Mimer
Mimer Information Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40
info@mimer.se
Mimer SQL Documentation TOC PREV NEXT INDEX