C:/>sqlplus "/ as sysdba"
SQL*Plus: Release 9.0.1.0.1 - Production on Thu Aug 8 09:20:57 2002
(c) Copyright 2001 Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.0.1.1.1 - Production
With the Partitioning option
JServer Release 9.0.1.1.1 - Production
SQL> select count(*) from dual;
COUNT(*)
----------
1
SQL> select * from dual;
D
-
X
SQL> insert into dual values ('Y');
1 row created.
SQL> commit;
Commit complete.
SQL> insert into dual values ('X');
1 row created.
SQL> insert into dual values ('Z');
1 row created.
SQL> commit;
Commit complete.
SQL> select count(*) from dual;
COUNT(*)
----------
4
SQL> select * from dual;
D
-
X
SQL> select sysdate from dual;
SYSDATE
---------
08-AUG-02
SQL> select count(*) from dual;
COUNT(*)
----------
4
SQL> truncate table dual;
Table truncated.
SQL> select count(*) from dual;
COUNT(*)
----------
0
SQL> select * from dual;
no rows selected
SQL> select sysdate from dual;
no rows selected
SQL> insert into dual values ('X');
1 row created.
SQL> commit;
Commit complete.
SQL> select * from dual;
D
-
X
SQL> select count(*) from dual;
COUNT(*)
----------
1
SQL> select sysdate from dual;
SYSDATE
---------
08-AUG-02
SQL>
***************************************
作者:4pal 时间:02-08-08 22:01
嘿嘿。snow知道dual到底是什么吗? 我还是不 清楚
作者:rejoice999 时间:02-08-08 23:55
DUAL就是个一行一列的表,如果你往里加一行,就会导致很多程序出问题。所以从ORACLE8开始,ORACLE加了代码对DUAL特殊照顾,才会有SNOW版主的FUNNY TEST RESULT。
http://www.itpub.net/showthread.php...&highlight=dual
quote:
最初由 4pal 发布
嘿嘿。snow知道dual到底是什么吗? 我还是不 清楚
作者:oldwain 时间:02-08-10 21:19
quote:
最初由 rejoice999 发布
所以从ORACLE8开始,ORACLE加了代码对DUAL特殊照顾,
NO! NO!
ORACLE没有对DUAL进行特殊照顾, 进行特殊照顾的是sql*plus.
使用其它工具(比如pl/sql dev等) 会发现select * from dual会得到真实的记录.
另外, 在sqlplus中执行create table .. as select * from dual , inset ..select * from dual的结果也是真实的.
个人认为sqlplus耍的这个小聪明, 是个很愚蠢的小聪明.
作者:Fenng 时间:02-08-10 23:24
跟着这个贴子看了看,随后到asktom上查了一下,发现还真有贴子关于它的.
You Asked
Hi Tom
Feels good to post a question after quite some time.
Look at the following :
SQL> desc dual
Name Null? Type
----------------------------------------- -------- ----------------------------
DUMMY VARCHAR2(1)
SQL> select * from dual;
D
-
X
SQL> select count(*) from dual;
COUNT(*)
----------
1
SQL> select 'sdfsdfsdfsdfsdfsdf' from dual;
'SDFSDFSDFSDFSDFSD
------------------
sdfsdfsdfsdfsdfsdf
SQL> select 3434334 from dual;
3434334
----------
3434334
SQL> truncate table dual;
truncate table dual
*
ERROR at line 1:
ORA-04020: deadlock detected while trying to lock object
3510531527724648449742036
SQL> delete from dual;
delete from dual
*
ERROR at line 1:
ORA-01031: insufficient privileges
SQL> connect system/manager
Connected.
SQL> /
1 row deleted.
SQL> commit;
Commit complete.
SQL> select * from dua;
select * from dua
*
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> select * from dual;
no rows selected
1.What is the dual table, what is its purpose.
2.Why does it contain only one column with datatype varchar2, why not
number .
3.Does it contain one row by default.
4.why do we
usually SELECT USER FROM DUAL,
why cant I do it like
SQL> select USER FROM EMP WHERE ROWNUM<2;
USER
------------------------------
SCOTT
5.Does this mean that we are using the dual table only for the convenience that
it has only one row, and it will return only one row back , when we give
queries like
SELECT USER FROM DUAL
6.SQL> SELECT COUNT(*) FROM DUAL;
COUNT(*)
----------
2
SQL> INSERT INTO DUAL VALUES ('X');
1 row created.
SQL> INSERT INTO DUAL VALUES ('X');
1 row created.
SQL> COMMIT;
Commit complete.
SQL> SELECT COUNT(*) FROM DUAL;
COUNT(*)
----------
4
SQL> SELECT * FROM DUAL;
D
-
X
Why is it returning only one row , it has to return 4 rows , when it has allowed
me to insert 4 rows.
7.SQL> delete from dual;
1 row deleted.
SQL> select * from dual;
D
-
X
SQL> select count(*) from dual;
COUNT(*)
----------
3
I want to delete all the rows , I do a delete from dual, and oooo mama
look at it , it deletes only one row, why?
8.SQL> delete from dual;
1 row deleted.
SQL> delete from dual;
1 row deleted.
SQL> select count(*) from dual;
COUNT(*)
----------
1
NOw we have only one row in dual.
lets create a example function.
SQL> create or replace function foo return number
2 as
3 x number;
4 begin
5 x:=1;
6 return 1;
7 end;
8 /
Function created.
SQL> select foo from dual;
FOO
----------
1
SQL> insert into dual values ('X');
1 row created.
SQL> COMMIT;
Commit complete.
SQL> SELECT COUNT(*) FROM DUAL;
COUNT(*)
----------
2
SQL> select foo from dual;
FOO
----------
1
shouldnt it return 2 rows of value 1?
because , look below , I have got 14 rows back , because I had 14 rows in the
table.
SQL> SELECT FOO FROM EMP;
FOO
----------
1
1
1
1
1
1
1
1
1
1
1
FOO
----------
1
1
1
14 rows selected.
SQL>
Kindly elucidate the concept of dual table, and if possible illustrate it.
Thank you
--------------------------------------------------------------------------------
and we said...
Let me just start by saying -- DUAL is owned by SYS. SYS owns the data dictionary, therefore DUAL is part of the data dictionary. You are not to modify the data dictionary via SQL ever -- wierd things can and will happen -- you are just demonstrating some of them. We can make many strange things happen in Oracle by updating the data dictionary. It is neither recommend, supported nor a very good idea.
1.What is the dual table, what is its purpose.
dual is just a convienence table. You don't need to use it, you can use anything you want. The advantage to dual is the optimizer understands dual is a special one row, one column table -- when you use it in queries, it uses this knowledge when developing the plan.
2.Why does it contain only one column with datatype varchar2, why not
number .
truly, why no. Why not a date you would ask then. The column, its name, its datatype and even its value are NOT relevant. DUAL exists solely as a means to have a 1 row table we can reliably select from. Thats all.
3.Does it contain one row by default.
yes, when we build the database, we build dual and put a single row in it.
4.why do we usually SELECT USER FROM DUAL,
why cant I do it like
SQL> select USER FROM EMP WHERE ROWNUM<2;
truly, why can't you? is something preventing you from doing so?? You can if you want. Me, I'll stick with "select user from dual". I know dual exists. I know it has at least 1 and at most 1 row. I know the optimizer knows all about dual and does the most efficient thing for me.
5) yes
6) the optimizer understands dual is a magic, special 1 row table. It stopped on the select * because there is to be one row in there. Its just the way it works. Hopefully you reset dual back to 1 row after your testing or you just totally broke your database!
7) like I said, duals magic, the optimizer knows all about what DUAL should be and does things based on that.
8) dual = magic. dual is a one row table however having more then 1 or less then one is dangerous. You are updating the data dictionary. You should naturally expect very bad things to happen.
Ok, here is some trivia for you out there. How did I do this:
SVRMGR> select * from dual;
D
-
X
1 row selected.
SVRMGR> ????????????????????;
Statement processed.
SVRMGR> select * from dual;
ADDR INDX INST_ID D
-------- ---------- ---------- -
01680288 0 1 X
1 row selected.
What was that magic command?
作者:Fenng 时间:02-08-10 23:26
http://asktom.oracle.com/pls/ask/f?...6388,%7Bdual%7D
这是Tom上的连接
作者:biti_rainy 时间:02-08-11 09:49
hehe
看了 关于定义者权限和调用者权限 部分,结合oracle的关于所谓“精细存取控制”
在使用 sys_context() 函数的基础上
自己都可以做这么一个表出来
并且可以做一个满足你的需要的比dual更让你满意的表