Revamped ON clause for drag and drop views

Larry Beasley shared this problem ago

Completed

I would log this as an idea but it's a real challenge creating ON clauses that look like this:

Conditions should localized to the table ON clause rather than the where clause:

LEFT JOIN TABLE1 ON 
     TABLE1.table1_id = TABLE2.table1_id
     AND TABLE1.sometextfield = 'Geo Location'

When using the condition that appears to be tied to the table the actual condition is sent to the where clause. Doing so, creates an entirely different and unwanted effect. Here's what actually happens when you add the condition to TABLE1:

LEFT JOIN TABLE1 ON 
 TABLE1.table1_id = TABLE2.table1_id
WHERE TABLE1.sometextfield = 'Geo Location'

The two results are different because inserting the condition into the WHERE clause forces the query into an INNER JOIN instead of the desired LEFT JOIN.

The same problem 0

Replies (5)

Chegudi Priya ●

Hello Larry Beasley,

My name is Chegudi Priya from the Yellowfin Technical Support Team. We have received your support request, and I will be your primary contact on the following ticket:

Ticket Number: #32225-04-03
Case Title: Revamped ON clause for drag and drop views

Please allow us some time we will get back to you shortly. If you have any further questions or need assistance, please reach out to us. We're here to help.

Thanks & Regards,

Priya.

Reply URL

Chegudi Priya ●

Hello Larry Beasley,

Thank you for your patience, The specific information about localizing conditions to the table ON clause rather than the WHERE clause in Yellowfin. However, it does mention that table conditions permit you to limit the data returned from a specific table and provides details on how to create and manage conditions.

For more detailed information on table conditions, you can refer to the official documentation here: Table Conditions.

Thanks & Regards,

Priya.

Reply URL

Larry Beasley ●

Hi Priya,

edited below

Thanks for responding so fast. You're right. I tried to duplicate the issue and I think that I might have had the condition in the primary table and in that case it will place the condition in the where clause. THANKS!

While the above works for drag and drop tables my issue stems from when using a virtual table. I would send a screenshot but it's easy to try. Virtual table conditions drop to the where clause.

Reply URL

Chegudi Priya ●

Hello Larry Beasley,

I wanted to let you know that we’re currently unable to proceed with your request, as we do not have your credentials or any associated records on file. If you are a Credible customer, please contact Credible directly so they can assist you further.

Feel free to reach out if you have any questions or need help with anything else.

Reply URL

Chegudi Priya ●

Hello Larry Beasley,

I am going to go ahead and mark this ticket as Completed for now. However, feel free to reach out if you have any questions or need help with anything else.

Reply URL