oracle 递归查询-个人总结
首先,建表: create table T_TEST_WORD( id NUMBER, pid VARCHAR2(20), name VARCHAR2(20)) 插入数据: insert into T_TEST_WORD (id, pid, name)values (1, '-1', '中国');insert into T_TEST_WORD (id, pid, name)values (2, '1', '江苏');insert into T_
首先,建表:
create table T_TEST_WORD ( id NUMBER, pid VARCHAR2(20), name VARCHAR2(20) )
插入数据:
insert into T_TEST_WORD (id, pid, name) values (1, '-1', '中国'); insert into T_TEST_WORD (id, pid, name) values (2, '1', '江苏'); insert into T_TEST_WORD (id, pid, name) values (3, '1', '浙江'); insert into T_TEST_WORD (id, pid, name) values (4, '2', '南京'); insert into T_TEST_WORD (id, pid, name) values (5, '2', '无锡'); insert into T_TEST_WORD (id, pid, name) values (6, '1', '安徽'); insert into T_TEST_WORD (id, pid, name) values (7, '4', '雨花台区'); insert into T_TEST_WORD (id, pid, name) values (8, '-1', '美国'); insert into T_TEST_WORD (id, pid, name) values (9, '-1', '俄罗斯'); commit;
查询下表中的数据:
表1
其中PID为-1的代表根节点。
开始进行递归查询:
查询结果如下:
表2
说明:
select ... from tablename(表名) where 条件1 start with 条件2 connect by 条件3 and 条件4 ...
看下这个语句(由根节点向子节点查询):
select t.* , level from T_TEST_WORD t start with pid='-1' connect by prior
id = pid(由根节点向子节点查询)
从T_TEST_WORD表中查询所有记录,从pid=-1的开始查询,且上一次查询记录的id作为本次查询的pid,以上表为例,举例如下:
第一次查询出pid=-1的记录是id为1的那条。
第二次查询时,查询pid=1的(上次查询记录的id是1)记录,可以查询到id为2的那条记录
第三次查询时,查询pid=2的(上次查询记录的id是2)记录,可以查询到id为4的那条记录,以此类推......
由上,查询到了表2的记录。
由树的根节点向子节点查询时,查询节点的顺序是按照树的前序遍历(DLR)进行的(1,2,4,7,5,3,6,8,9),如下图1
图1:
(比较丑的图,凑合看吧,嘻嘻)
注意:那个level要有start with ...... connect by ...... 才有效哦,不然会报错的。
再看这句(由子节点向根节点查询):
select t.* ,level from T_TEST_WORD t start with pid='2' connect by id = prior pid
从pid=2的开始(向上)查询,且上一次查询记录的pid作为本次查询的id
prior挨着谁,就将谁作为本次查询的某某关键字,比如connect by id = prior pid,就是将上次的pid作为本次查询的id。
注意,level是伪列,查询数据所对应的级,或者说深度吧。
小菜的总结,有问题请指出,谢谢咯!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The retention period of Oracle database logs depends on the log type and configuration, including: Redo logs: determined by the maximum size configured with the "LOG_ARCHIVE_DEST" parameter. Archived redo logs: Determined by the maximum size configured by the "DB_RECOVERY_FILE_DEST_SIZE" parameter. Online redo logs: not archived, lost when the database is restarted, and the retention period is consistent with the instance running time. Audit log: Configured by the "AUDIT_TRAIL" parameter, retained for 30 days by default.

The Oracle database startup sequence is: 1. Check the preconditions; 2. Start the listener; 3. Start the database instance; 4. Wait for the database to open; 5. Connect to the database; 6. Verify the database status; 7. Enable the service (if necessary ); 8. Test the connection.

To find the number of occurrences of a character in Oracle, perform the following steps: Get the total length of a string; Get the length of the substring in which a character occurs; Count the number of occurrences of a character by subtracting the substring length from the total length.

Oracle database server hardware configuration requirements: Processor: multi-core, with a main frequency of at least 2.5 GHz. For large databases, 32 cores or more are recommended. Memory: At least 8GB for small databases, 16-64GB for medium sizes, up to 512GB or more for large databases or heavy workloads. Storage: SSD or NVMe disks, RAID arrays for redundancy and performance. Network: High-speed network (10GbE or higher), dedicated network card, low-latency network. Others: Stable power supply, redundant components, compatible operating system and software, heat dissipation and cooling system.

The amount of memory required by Oracle depends on database size, activity level, and required performance level: for storing data buffers, index buffers, executing SQL statements, and managing the data dictionary cache. The exact amount is affected by database size, activity level, and required performance level. Best practices include setting the appropriate SGA size, sizing SGA components, using AMM, and monitoring memory usage.

To create a scheduled task in Oracle that executes once a day, you need to perform the following three steps: Create a job. Add a subjob to the job and set its schedule expression to "INTERVAL 1 DAY". Enable the job.

The amount of memory required for an Oracle database depends on the database size, workload type, and number of concurrent users. General recommendations: Small databases: 16-32 GB, Medium databases: 32-64 GB, Large databases: 64 GB or more. Other factors to consider include database version, memory optimization options, virtualization, and best practices (monitor memory usage, adjust allocations).

Oracle can read dbf files through the following steps: create an external table and reference the dbf file; query the external table to retrieve data; import the data into the Oracle table.
