ANSI inner join syntax

Hi,
Is there a way to configure BI Server 11g to generate ANSI join sytax ("INNER JOIN" clause) for Oracle, as it does when using OUTER JOINs?
Thank you.

OBIEE will not generate ANSI syntax for Inner Joins and as you said it only generates for Outer joins. Hope this clears your doubt.

Similar Messages

ANSI/9i Join Syntax and Pretty Code

I've always tried to keep my SQL statement code formatted in a way that I think helps readability. I picked up the following style because I found it easy to quickly find the FROM clause and the JOINS or conditions:
select e.ename,
       e.sal,
       d.dname
from   emp e,
       dept d
   * Joins
where e.deptno = d.deptno
   * Conditions
and    d.dname = 'SALES'
/Of course, for such a simple query I wouldn't have used the comments to divide the WHERE clause into joins and conditions...
Anyway, since Tom Kyte and the 9i documentation suggest using the ANSI join syntax (amongst other reasons), I have decided to begin changing my ways. However, I am having troubles figuring out how to format my SQL to still be "pretty."
For the previous example, a new formatting style seems easy:
select e.ename,
       e.sal,
       d.dname
from   emp e
join dept d          on e.deptno = d.deptno
where d.dname = 'SALES'
/Now, when we use an example that has optional joins is where I can't figure what my style should be:
select e.ename,
       m.ename as manager
from        emp e
left join emp m      on e.mgr = m.empno
where e.deptno = 10
/I don't really like this style since it gets so wide, causing problems when indenting for subqueries/inline-views. It also looks kinda clunky because the tables are indented more than everything else...
Anyway, since I don't want to spend a bunch of time figuring out things like style, I'd like to see what other formats people are using. I'd appreciate seeing how others are formatting thier SQL when using the new 9i (old-ANSI) syntax.
Thanks, Stan

That looks to me like left aligned (but I may be on the wrong side of the looking glass...)
By preference is to left-align the KEYWORDS and the data words, using indentation to distinguish the start of the different clauses (SELECT, FROM, WHERE, ORDER BY, etc.). This approach is easily standardised with Textpad or similar editing tools. Quite how one programs a text editor to turn one's code into a Rorschach blot is beyond me.
I haven't done much with ANSI joins, so I hadn't come up with a standard for layout. The following is what I think I would do if I ever had to, and is basically an adaption of what I do now ...
FROM   user_indexes i
       , user_ind_columns ic2
       , user_tab_columns c2with the ANSI join stuff indented and aligned. I find rigourous application of UPPER and lower case tends to assist clarity: indentation and alignment are not enough.
SELECT i.table_name
       , i.index_name
       , ic2.column_position
FROM   user_indexes i
       INNER JOIN user_ind_columns ic2
       ON i.table_name = ic2.table_name
       AND i.index_name = ic2.index_name
       INNER JOIN user_tab_columns c2
       ON ic2.table_name = c2.table_name
       AND ic2.column_name = c2.column_name
WHERE i.uniqueness='UNIQUE'
ORDER BY i.table_name
       , i.index_name
       , ic2.column_position
/

Drag-n-n-drop query joins uses WHERE, not INNER JOIN syntax

When I highlight a few tables and drag them onto the sql worksheet, it will build a select statement for me and join the tables by their foreign keys.
That's a nice feature, thanks!
Three questions. Is it possible to:
1. get it to use the INNER JOIN and LEFT OUTER JOIN syntax instead of joining the tables in the WHERE clause?
2. control the table aliases so that it will automatically use the "standard alias" for the table instead of A, B, C, etc.?
3. get it to not put the schema name into the query?
Thanks!
Edited by: David Wendelken on Nov 22, 2008 1:48 PM. Grammar mistake.

Hi Gopi,
Your code is Good.
But try to avoid Inner join with more number of Tables ...because this is a performance issue..
try to use..
select (primary key fields mainly,other fields) from LIKP into itab where bolnr in p_bolnr(paramater).
next try to use for all entries option..
select (primary key fields mainly,other fields) from VBFA for all entries in itab where (give the condition)....
simillarly do for the other select ....ok this will try to reduce the performance issue....
<b><REMOVED BY MODERATOR></b>
Message was edited by:
Alvaro Tejada Galindo

ANSI/ISO JOIN SYNTAX

DEAR Friends,
How can i write the ansi/iso syntax for below query
select a.company,b.fpm_ac_code from facmast a,fparty b, fstatus c
where a.company = b.company(+)
and a.fac_ac_code = b.fpm_ac_code(+)
and a.company = c.company(+)
one method is
select a.company ,b.fpm_ac_ccode from facmast a right outer join fparty b on a.company = b.company
and a.fac_ac_code = b.fpm_ac_code
,facmast c right outer join fstatus d on c.company = d.company
but this is equivalent
select a.company,b.fpm_ac_code from facmast a,fparty b,facmast c, fstatus d
where a.company = b.company(+)
and a.fac_ac_code = b.fpm_ac_code(+)
and c.company = d.company(+)
pls help me
Siddharth singh

I would transpose this statement...
select a.company, b.fpm_ac_code
from facmast a, fparty b, fstatus c
where a.company = b.company(+)
and a.fac_ac_code = b.fpm_ac_code(+)
and a.company = c.company(+)
into this...
SELECT a.company, b.fpm_ac_code
FROM facmast a
LEFT OUTER JOIN fparty b
ON a.company = b.company
AND a.fac_ac_code = b.fpm_ac_code
LEFT OUTER JOIN fstatus c
ON a.company = c.company
I think this may be closer to what you want.
Remember, the (+) goes on the side that is deficient in information; but the LEFT or RIGHT keyword points to the table on the side of the JOIN clause (not the ON condition) from which you want information.
Best!

SYNTAX "INNER JOIN and OUTER JOIN"

Hi Experts,
I think LEFT JOIN,INNER JOIN syntax is in ANSI.
I know that Oracle has got its own alternate(+) operator to serve the purpose.
Please tell me whether INNER JOIN,OUTER JOIN,LEFT JOIN,LEFT OUTER JOIN,RIGHT OUTER JOIN these syntaxes present in ORACLE 8I.
If not in 9i Or highr versions are they existing?
Thanks in advance,
Ananth
null

Hi,
8i has inner join. (+) syntax supports LEFT or RIGHT OUTER JOIN.
FULL OUTER JOIN is supported in 9i, which introduces the JOIN keyword.
Herman

Does INNER JOIN work with Oracle 8i ? (ORA-00933)

hi,
I try to execute the sql:
SELECT
A0.FULL_NAME,A0.MANAGER_ID,A0.DEPT_NO,A0.TOP_DEPT
FROM
HR_ORG A0
INNER JOIN
HR_EMP A1
ON
A0.MANAGER_ID=A1.EMP_NO
WHERE
A1.NAME = 'michael'
but I caught an exception:
java.sql.SQLException: ORA-00933: SQL...(message in
chinese)
Does INNER JOIN work with Oracle 8i ?
thanks.

INNER JOIN syntax is introduced in 9i, it does not exists in 8i. You can rewrite your statement:
SELECT
A0.FULL_NAME,A0.MANAGER_ID,A0.DEPT_NO,A0.TOP_DEPT
FROM
HR_ORG A0
, HR_EMP A1
WHERE
A0.MANAGER_ID=A1.EMP_NO
AND
A1.NAME = 'michael'

Flow accept error when using ANSI join syntax

Hi
I had a region populated by a query joining two views (one in-line using connect by). When trying to create the region if the join was coded using ANSI syntax (INNER JOIN .... USING) I got a flow accept error when either trying to proceed using the wizard, or apply changes when editing the region.
After changing to the old style Oracle join (using predicates), I was able to create the region and everything worked ok. I found the solution after reading this post Error 404 wwv_flow.accept was not found in which the OP says he would raise a bug. Did the bug get raised? I ask since his problem arose whilst he was selecting from a view using ANSI joins and using instead of triggers, and I was joining an in-line view to a view using ANSI joins and instead of triggers, but neither view has been changed, just the join syntax. The view defined in the database is used in other regions and works fine. This could indicate the OP's problem was fixed, but one still exists.
Incidentally this is the only time I have used non-ANSI joins in the entire apex app - the rest work!. Unfortunately it is impossible for me to demo the app.
Richard
using ApEx 3.0.1.00.07 and 10g (10.2.0.1) EE on Wintel

Tyler,
Apologies, what I was trying to say was that I couldn't put the application on the Oracle APEX site.
Yes, I do have a work-around, but that does not mean a bug may still exist. I count myself fortunate I saw that post and, therefore, experimented with the syntax of the join - there is no reason APEX should not accept ANSI join conditions, in fact , it does. The ANSI-joined SQL statement executed perfectly in TOAD and SQL*Plus, but I could not even save it in APEX.
regards
Richard

Use ansi join syntax

From what i have been reading is better to use the new syntax(dont know how new it is)

The ANSI join syntax was new to Oracle in Oracle 8i in 1998 - that's 15 years old.
It can produce more readable code, and is both more readable and less human-error prone for outer joins.
The ANSI format lets you outer join between multiple tables in a way the old oracle-specific ( + ) syntax did not and introduces FULL OUTER JOIN which you should use very rarely.
You should not use NATURAL JOIN in code - adding unrelated columns to the tables involved can make it give very different results.
There have not been significant bugs for ANSI joins in Oracle since Oracle 10.2 was introduced about 8 years ago.
As Paul said, the ON part should be the join criteria between the tables. The were clause should be the filtering of the joined tables.
So assuming start_date, end_date and in_property_id are variables
SELECT resv_num, unit_date
    FROM p_resv_unit ru
    INNER JOIN p_pm_unit_night pun
    ON pun.resv_unit_id = ru.resv_unit_id
    WHERE pun.property_id = in_property_id
    AND pun.unit_date BETWEEN start_date AND end_date
    AND pun.pm_unit_num = cvUnitNum;
If start_date and end_date were columns in p_resv_unit the query would be:
SELECT resv_num, unit_date
    FROM p_resv_unit ru
    INNER JOIN p_pm_unit_night pun
    ON pun.resv_unit_id = ru.resv_unit_id AND pun.unit_date BETWEEN ru.start_date AND ru.end_date
    WHERE pun.property_id = in_property_id
        AND pun.pm_unit_num = cvUnitNum;
Inner join queries work with criteria in the wrong place, but they're harder to read. Outer joins don't work unless you put the criteria in the right place.

What is syntax for inner join of Select statement with Secondary Index

Hi Genies,
                Here i have created the Secondary index for table COEP and also used for select query but there is no improvement in runtime . taking same time for select query without index as well as with index. my code is
SELECT * INTO CORRESPONDING FIELDS OF TABLE ITAB_COEP FROM COEP AS A
             INNER JOIN COBK AS B ON ( A~BELNR = B~BELNR AND A~KOKRS = B~KOKRS AND A~GJAHR = B~GJAHR )
             WHERE A~OBJNR = OBJNR
             AND A~GJAHR = CURRY
             AND B~GJAHR = CURRY
             AND A~RBEST = ''
             AND A~BEKNZ = 'S'
             AND B~BELNR NE WA_COBK-BELNR
             AND B~AWREF_REV = ''
             AND B~AWORG_REV = ''
             AND B~KOKRS = WA_COIOB-KOKRS
             AND B~BLDAT BETWEEN START_DATE AND END_DATE
             AND B~BLART IN ('SA','KA','KR','AB') %_HINTS ORACLE 'INDEX("COEP" "COEP~ZBU")'.
index name is ZBU.
please any one let me know is there any syntax mistakes? but while checking and during the runtime it does'nt shows any error.
Regards,
        Thangam.P

Hi Genies,
                Here i have created the Secondary index for table COEP and also used for select query but there is no improvement in runtime . taking same time for select query without index as well as with index. my code is
SELECT * INTO CORRESPONDING FIELDS OF TABLE ITAB_COEP FROM COEP AS A
             INNER JOIN COBK AS B ON ( A~BELNR = B~BELNR AND A~KOKRS = B~KOKRS AND A~GJAHR = B~GJAHR )
             WHERE A~OBJNR = OBJNR
             AND A~GJAHR = CURRY
             AND B~GJAHR = CURRY
             AND A~RBEST = ''
             AND A~BEKNZ = 'S'
             AND B~BELNR NE WA_COBK-BELNR
             AND B~AWREF_REV = ''
             AND B~AWORG_REV = ''
             AND B~KOKRS = WA_COIOB-KOKRS
             AND B~BLDAT BETWEEN START_DATE AND END_DATE
             AND B~BLART IN ('SA','KA','KR','AB') %_HINTS ORACLE 'INDEX("COEP" "COEP~ZBU")'.
index name is ZBU.
please any one let me know is there any syntax mistakes? but while checking and during the runtime it does'nt shows any error.
Regards,
        Thangam.P

ANSI SQL 92 SYNTAX OUTER JOIN PERFORMANCE ISSUE

Good Morning
Could anyone explain why the excution time for these two (ment to be identical)
queries run so differently.
oracle syntax execution time 1.06 seconds
select COUNT(*) from
PL_EVENT_VIEW pev,
PL_EVENT_STAFF_VIEW pesv
WHERE pev.EVENT_ID=PESV.EVENT_ID(+)
AND pev.WEEKS=PESV.WEEK_NUM(+)
AND pev.event_id=2520
ansi sql 92 syntax execution time 7.05 seconds
select COUNT(*) from
PL_EVENT_VIEW pev
LEFT JOIN PL_EVENT_STAFF_VIEW pesv
ON (pev.EVENT_ID=PESV.EVENT_ID
AND pev.WEEKS=PESV.WEEK_NUM)
WHERE pev.event_id=2520
Thanks
David Hills

BTW Oracle outer join operator (+) and ANSI SQL OUTER JOIN syntax are NOT equivalent. Consider following:
DROP TABLE T1;
CREATE TABLE T1 (C1 NUMBER);
DROP TABLE T2;
CREATE TABLE T2 (C2 NUMBER);
DROP TABLE T3;
CREATE TABLE T3 (C3 NUMBER);
-- Following SELECT works:
SELECT COUNT(*)
     FROM T1, T2, T3
     WHERE C2 = C1
          AND C3(+) = C1
COUNT(*)
0
-- But:
SELECT COUNT(*)
     FROM T1, T2, T3
     WHERE C2 = C1
          AND C3(+) = C1
          AND C3(+) = C2
AND C3(+) = C1
ERROR at line 4:
ORA-01417: a table may be outer joined to at most one other table
-- However with ANSI syntax:
SELECT COUNT(*)
     FROM T1
     JOIN T2 ON (C2 = C1)
     LEFT JOIN T3 ON (C3 = C1 AND C3 = C2)
COUNT(*)
0

Syntax errors in update query with inner joins and sub query.

Below is the query:
UPDATE sp_CFQ_Coord_Corrections
INNER JOIN (CFQ_Coord_Corrections
INNER JOIN CFQ_Referrals ON CFQ_Coord_Corrections.CorrID = CFQ_Referrals.RecID)
ON sp_CFQ_Coord_Corrections.ID = CFQ_Referrals.RecID
SET CFQ_Coord_Corrections.MatchFound = 1,
CFQ_Coord_Corrections.RecTblID = [CFQ_Referrals].[RecTblID],
sp_CFQ_Coord_Corrections.MatchFound = 1
WHERE (((CFQ_Coord_Corrections.MatchFound)=0)
AND ((sp_CFQ_Coord_Corrections.MatchFound)=0)
AND ((CFQ_Coord_Corrections.RecImported)=1)
AND ((CFQ_Referrals.RecFileName)='COORDCORR_SPOINT')
AND ((CFQ_Referrals.RecCombKey)='No.Match')
AND ((sp_CFQ_Coord_Corrections.RecImported)=1));
Error messages seen when executed:
Msg 156, Level 15, State 1, Line 3
Incorrect syntax near the keyword 'INNER'.
Msg 102, Level 15, State 1, Line 10
Incorrect syntax near 'CFQ_Coord_Corrections'.
Please help.....

Below is the query:
UPDATE sp_CFQ_Coord_Corrections
INNER JOIN (CFQ_Coord_Corrections
INNER JOIN CFQ_Referrals ON CFQ_Coord_Corrections.CorrID = CFQ_Referrals.RecID)
ON sp_CFQ_Coord_Corrections.ID = CFQ_Referrals.RecID
SET CFQ_Coord_Corrections.MatchFound = 1,
CFQ_Coord_Corrections.RecTblID = [CFQ_Referrals].[RecTblID],
sp_CFQ_Coord_Corrections.MatchFound = 1
WHERE (((CFQ_Coord_Corrections.MatchFound)=0)
AND ((sp_CFQ_Coord_Corrections.MatchFound)=0)
AND ((CFQ_Coord_Corrections.RecImported)=1)
AND ((CFQ_Referrals.RecFileName)='COORDCORR_SPOINT')
AND ((CFQ_Referrals.RecCombKey)='No.Match')
AND ((sp_CFQ_Coord_Corrections.RecImported)=1));
Error messages seen when executed:
Msg 156, Level 15, State 1, Line 3
Incorrect syntax near the keyword 'INNER'.
Msg 102, Level 15, State 1, Line 10
Incorrect syntax near 'CFQ_Coord_Corrections'.
Please help.....
sp_CFQ_Coord_Corrections is a table and not a stored procedure.
are these both tables "sp_CFQ_Coord_Corrections" and "CFQ_Coord_Corrections" different ??

Difference between oracle join syntaxes and ANSI join syntaxes

What is difference between oracle join syntaxes and ANSI join syntaxes ?
why oracle is having different syntaxes for joins than ANSI syntaxes ?
Also Join syntaxes are different in some oracle vesrions ?

BluShadow wrote:
3360 wrote:
Yes it is. The Oracle database wasn't initially designed to be ANSI compliant. As you correctly state the ANSI standards weren't around when it was initially designed, so the statement is perfectly correct. ;)Ok, in one sense it may be correct but it is a completely misleading statement. Not sure why you think it's misleading.Because there was no ANSI standard, so making it sound like a design choice The Oracle database wasn't initially designed to be ANSI compliant. would suggest to most readers that there was a standard to be compliant to.
Like saying Ford originally did not design their cars to incorporate safety features such as ABS, seat belts and air bags.
The OP asked "why oracle is having different syntaxes for joins than ANSI syntaxes ?" and the answer is that Oracle wasn't initially designed with ANSI compliance, so it has it's old non-ANSI syntax,As shown above, the old syntax was ANSI compliant at the time and to call it non-ANSI is either incorrect or misleading dependent on your point of view.
and since ANSI syntax became the standard it now supports that. And since ANSI switched to a new standard, Oracle had to implement the new standard as well as the previous ANSI standard would be more accurate in my opinion.
Nothing misleading as far as I'm aware in that.I find the whole discussion about ANSI and Oracle's supposed non-compliance, reads like it was Oracle's choice to deviate from the standards, when it was ANSI's bullheaded decisions to pointlessly change standards that left Oracle and other vendors out of compliance, and that was a decision made solely by ANSI.
This is probably the reason ANSI no longer produces SQL standards, the endless syntax fiddling would eventually have made forward left under outer joins a reality.
{message:id=1785128}

ANSI join syntax with code-insight

I've noticed that SQL Developer 1.1.3 doesn't perform code-insight into table aliases when I use the ANSI join sytax. Is there a configuration option to make this possible or does it just not exist yet?

Hi,
Currently on SQL Developer 1.2, Windows XP, and Database 9.2
I have the same problem too.
The Code-Insight is unable to show the Code Completion for aliased table name in ANSI JOIN
SELECT *
FROM    Schema1.Table1 t1
INNER JOIN Schema1.Table2 t2 ON t2.     -- cannot show the code-insightHowever the following code works just fine for the code-insight
SELECT *
FROM    Schema1.Table1 t1,
              Schema1.Table2 t2
WHERE t1.Field1 = t2.Field1Any suggestion?
Regards,
Buntoro

Syntax of inner join

hello sir,
plz tell me the syntax of inner join for three tables.

Syntax
... [(] {dbtab_left [AS tabalias_left]} | join
{[INNER] JOIN}|{LEFT [OUTER] JOIN}
{dbtab_right [AS tabalias_right] ON join_cond} [)] ... .
Effect
The join syntax represents a recursively nestable join expression. A join expression consists of a left-hand and a right- hand side, which are joined either by means of [INNER] JOIN or LEFT [OUTER] JOIN . Depending on the type of join, a join expression can be either an inner ( INNER) or an outer (LEFT OUTER) join. Every join expression can be enclosed in round brackets. If a join expression is used, the SELECT command circumvents SAP buffering.
On the left-hand side, either a single database table, a view dbtab_left, or a join expression join can be specified. On the right-hand side, a single database table or a view dbtab_right as well as join conditions join_cond can be specified after ON. In this way, a maximum of 24 join expressions that join 25 database tables or views with each other can be specified after FROM.
AS can be used to specify an alternative table name tabalias for each of the specified database table names or for every view. A database table or a view can occur multiple times within a join expression and, in this case, have various alternative names.
The syntax of the join conditions join_cond is the same as that of the sql_cond conditions after the addition WHERE, with the following differences:
At least one comparison must be specified after ON.
Individual comparisons may be joined using AND only.
All comparisons must contain a column in the database table or the view dbtab_right on the right-hand side as an operand.
The following language elements may not be used: BETWEEN, LIKE, IN.
No sub-queries may be used.
For outer joins, only equality comparisons (=, EQ) are possible.
If an outer join occurs after FROM, the join condition of every join expression must contain at least one comparison between columns on the left-hand and the right-hand side.
In outer joins, all comparisons that contain columns as operands in the database table or the view dbtab_right on the right-hand side must be specified in the corresponding join condition. In the WHERE condition of the same SELECT command, these columns are not allowed as operands.
Resulting set for inner join
The inner join joins the columns of every selected line on the left- hand side with the columns of all lines on the right-hand side that jointly fulfil the join_cond condition. A line in the resulting set is created for every such line on the right-hand side. The content of the column on the left-hand side may be duplicated in this case. If none of the lines on the right-hand side fulfils the join_cond condition, no line is created in the resulting set.
Resulting set for outer join
The outer join basically creates the same resulting set as the inner join, with the difference that at least one line is created in the resulting set for every selected line on the left-hand side, even if no line on the right-hand side fulfils the join_cond condition. The columns on the right-hand side that do not fulfil the join_cond condition are filled with null values.
Example
Join the columns carrname, connid, fldate of the database tables scarr, spfli and sflight by means of two inner joins. A list is created of the flights from p_cityfr to p_cityto. Alternative names are used for every table.
PARAMETERS: p_cityfr TYPE spfli-cityfrom,
p_cityto TYPE spfli-cityto.
DATA: BEGIN OF wa,
fldate TYPE sflight-fldate,
carrname TYPE scarr-carrname,
connid TYPE spfli-connid,
END OF wa.
DATA itab LIKE SORTED TABLE OF wa
WITH UNIQUE KEY fldate carrname connid.
SELECT ccarrname pconnid f~fldate
INTO CORRESPONDING FIELDS OF TABLE itab
FROM ( ( scarr AS c
INNER JOIN spfli AS p ON pcarrid = ccarrid
AND p~cityfrom = p_cityfr
AND p~cityto = p_cityto )
INNER JOIN sflight AS f ON fcarrid = pcarrid
AND fconnid = pconnid ).
LOOP AT itab INTO wa.
WRITE: / wa-fldate, wa-carrname, wa-connid.
ENDLOOP.
Example
Join the columns carrid, carrname and connid of the database tables scarr and spfli using an outer join. The column connid is set to the null value for all flights that do not fly from p_cityfr. This null value is then converted to the appropriate initial value when it is transferred to the assigned data object. The LOOP returns all airlines that do not fly from p_cityfr.
PARAMETERS p_cityfr TYPE spfli-cityfrom.
DATA: BEGIN OF wa,
carrid TYPE scarr-carrid,
carrname TYPE scarr-carrname,
connid TYPE spfli-connid,
END OF wa,
itab LIKE SORTED TABLE OF wa
WITH NON-UNIQUE KEY carrid.
SELECT scarrid scarrname p~connid
INTO CORRESPONDING FIELDS OF TABLE itab
FROM scarr AS s
LEFT OUTER JOIN spfli AS p ON scarrid = pcarrid
AND p~cityfrom = p_cityfr.
LOOP AT itab INTO wa.
IF wa-connid = '0000'.
WRITE: / wa-carrid, wa-carrname.
ENDIF.
ENDLOOP.
we r using 2 type of joins in abap they are
1) inner join.
this will join 2 tables using an common fiend and return the result with field values wich are common in both the tables
itab1 itab2
a b c a d
1 2 3 1 5
2 3 4 3 6
after innerjoining itab1 n itab2 on field a we wil get the o/p as
a b c d
1 2 3 5
only common field is taken..
2)left outer join
here it wil work in opossite way it will give values whic are not common
itab1 itab2
a b c a d
1 2 3 1 5
2 3 4 3 6
after left outer joining itab1 n itab2 on field a we wil get the o/p as
a b c d
2 3 4
only fields which are not common is taken from the left table..other field(d here) wil be empty
I think it will help u.
Reward Points if helpful.
Check for ALVROBOT.COM also it is also helpful.

Inner join query syntax

I have this query, however... I need the 'category' variable
to be 'LIKE' but the way I have it set up it doent work. Anyone
have an idea of how I might fix this.
<CFQUERY name="getworkshops" datasource="source">
SELECT m.category, m.proj_key, m.project, r.proj_key, r.url,
r.category, r.end_date, r.title, e.event_date, e.event_date_end,
e.category, e.proj_key
FROM (main m INNER JOIN resource r ON m.category LIKE
r.category)INNER JOIN event_cal e ON m.category LIKE e.category
WHERE m.category like '%workshop%' AND m.proj_key=r.proj_key
AND m.proj_key = e.proj_key
ORDER BY m.proj_key
</CFQUERY>

You could move your join statements to your where clause:
SELECT m.category, m.proj_key, m.project, r.proj_key, r.url,
r.category, r.end_date, r.title, e.event_date, e.event_date_end,
e.category, e.proj_key
FROM main m, resource r, event_cal e
WHERE m.category LIKE '%'+r.category+'%'
AND m.category LIKE '%" + e.category + '%'
AND m.category like '%workshop%' AND m.proj_key=r.proj_key
AND m.proj_key = e.proj_key
ORDER BY m.proj_key
I had to guess on how you wanted to match m.category against
resource and event_cal, but you get the idea.

ANSI inner join syntax

Similar Messages

Maybe you are looking for