SQL Standard
Date: Thu, 22 Apr 2010 02:52:23 +0000 (UTC)
Message-ID: <hqodl7$eer$1_at_news.eternal-september.org>
I am reading an old book about SQL standard, "A Guide to SQL Standard", by C.J. Date. On the page 87, the book lists some functions that are part of the SQL standard:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options
SQL> select current_user from
dual;
select current_user from dual
*
ERROR at line 1:
ORA-00904: "CURRENT_USER": invalid identifier
Elapsed: 00:00:00.15
SQL> select current_time() from
dual;
select current_time() from dual
*
ERROR at line 1:
ORA-00904: "CURRENT_TIME": invalid identifier
Elapsed: 00:00:00.13
SQL> select session_user from
dual;
select session_user from dual
*
ERROR at line 1:
ORA-00904: "SESSION_USER": invalid identifier
Elapsed: 00:00:00.13
SQL> select session_user() from
dual;
select session_user() from dual
*
ERROR at line 1:
ORA-00904: "SESSION_USER": invalid identifier
Elapsed: 00:00:00.14
SQL> show
session_user
SP2-0735: unknown SHOW option beginning "session_us..."
SQL> select bit_length('ABCD') from
dual;
select bit_length('ABCD') from dual
*
ERROR at line 1:
ORA-00904: "BIT_LENGTH": invalid identifier
Elapsed: 00:00:00.14
SQL>
I know that the vast majority of these functions has well known
equivalents in Oracle but I must say that I am curious about the reasons
for refusing to go with the standard.
-- http://mgogala.byethost5.comReceived on Wed Apr 21 2010 - 21:52:23 CDT