6 replies

**Is anyone else having issues with RLS

Is anyone else having issues with RLS and left joins?
We have optional relationships in our DB (i.e.

table_1

table_1

has a

table_2_id

table_2_id

which could be null), where it's relevant to us whether or not the relationships exist. We use Left Joins for this but having RLS defined on

table_2

table_2

thoughtspot forces an inner join.

More Details
As an example: we have

invoice

invoice

s and

customer

customer

s. An invoice may or may not have a customer, so the invoice's

customer_id

customer_id

may be null. We define the join between invoice and customer to be

left outer join

left outer join

, so that we can get all invoices regardless of whether or not they have a customer.

When the

customer

customer

table has no RLS, the query generates correctly, i.e.

FROM `invoice` AS `ta_3`
  LEFT OUTER JOIN `customer` AS `ta_2` ....

FROM `invoice` AS `ta_3`
  LEFT OUTER JOIN `customer` AS `ta_2` ....

but when we add an RLS rule to

customer

customer

, the engine seems to force an inner join

FROM `invoice` AS `ta_3`
  JOIN `customer` AS `ta_2` ....

FROM `invoice` AS `ta_3`
  JOIN `customer` AS `ta_2` ....

This is not good for us. We need to be able to include the

null

null

case for the customers as well.