Best Practices - WOrking with lot of fields

Question

I am working on new modules based on a migrated project. And I have
many fields to work with, which is making the code large and
repetitive (kind of). If I follow the existing structure (from
migration) it works fine but I am looking for better ways to do it.
I would appreciate any suggestions or experiences.
Thanks.
Sincerely,
Partha

Answer 1

Welcome to the forum!
I don't see anything obviously wrong with that SELECT statement. It looks very much like this query:
SELECT     e.ename, e.empno, e.mgr
,     d.deptno, d.dname
FROM     scott.emp     e
,     scott.dept     d
WHERE     e.deptno     = d.deptno
START WITH     e.empno          = 7566
CONNECT BY     PRIOR e.empno     = e.mgr
;which produces this output:
ENAME           EMPNO        MGR     DEPTNO DNAME
JONES            7566       7839         20 RESEARCH
SCOTT            7788       7566         20 RESEARCH
ADAMS            7876       7788         20 RESEARCH
FORD             7902       7566         20 RESEARCH
SMITH            7369       7902         20 RESEARCHIn the scott.emp table, empno is unique, and mgr is the empno of the boss, or parent . I assume employees.id is unique, and the employees.dependencia on any row is the boss of that employee.
Whenever you have a problem, it helps if you post a little sample data (CREATE TABLE and INSERT statements) and the results ypu want from that data, or give an example using commonly available tables, like those in the scott schema. Point out where the equery is getting the wrong results, say what the right results are in those places, and explain how you get those results from that data.
Always say which version of Oracle you're using (for example, 10.2.0.3.0).