Outer Joins Creates a Table Join Error
20 October, 2009
I am trying to create an outer join and it shows the message 'Tables are
not joined correctly'.
I want to see a list of all shareholders and their bank account if they
have one.
In the join popup I selected shareholder as the join from, outer join as
the join type, and bankaccount as the join to, is this a bug or am I doing
something wrong?
not joined correctly'.
I want to see a list of all shareholders and their bank account if they
have one.
In the join popup I selected shareholder as the join from, outer join as
the join type, and bankaccount as the join to, is this a bug or am I doing
something wrong?
When creating a join with inner joins the "direction" of the join is not relevant, but when creating an outer join the direction does matter. In the example you sent through, reversing the polarity on the outer-join would create a valid view, but this may not give the result that you were looking for.
The current limitation in Yellowfin is that an inner join cannot reside on the discretionary end of an outer join.
For example this will work:
CASE_PARTIES inner join CASE STAGES outer join TEAMS
But this will not work:
TEAMS outer join CASE_PARTIES inner join CASE STAGES
We are currently investigating algorithms to generate SQL based on complex "clumpings" of INNER JOINS seperated by OUTER JOINS. This will bracket together clumps of inner joins so that the SQL will best emulate the designers wishes.
If you require complex joins like this you can use a virtual table or use a hard-coded or SQL view.
The current limitation in Yellowfin is that an inner join cannot reside on the discretionary end of an outer join.
For example this will work:
CASE_PARTIES inner join CASE STAGES outer join TEAMS
But this will not work:
TEAMS outer join CASE_PARTIES inner join CASE STAGES
We are currently investigating algorithms to generate SQL based on complex "clumpings" of INNER JOINS seperated by OUTER JOINS. This will bracket together clumps of inner joins so that the SQL will best emulate the designers wishes.
If you require complex joins like this you can use a virtual table or use a hard-coded or SQL view.
The view builder has the limitation of not being able to have an INNER JOIN on the discretionary end of an OUTER JOIN. The simple answer to this problem is that you probably want to create the join in the other direction. Create the join "backwards" as outer joins have "polarity".
So if you are currently creating a outer join from Table A to Table B, go to Table B and create the outer join back to Table A instead. I am guessing this will solve your problem.
So if you are currently creating a outer join from Table A to Table B, go to Table B and create the outer join back to Table A instead. I am guessing this will solve your problem.