RLS via Plugin? about kysely

[koskimas]

However, the challenge with this approach, is that the querybuilder requires that I know the type when building the query.

I'm not following. What do you mean? What type of what query? The query in the plugin?

[gdbjohnson]

@koskimas : essentially, for every Select query that applies this plugin, I want to add "orgCode = X" in the where clause, for all queries. The idea is to abstract out the handling of meta data to a central place, so that devs working on business logic don't have to think about it. By centralizing it here, we can ensure better guarantees of consistent handling of this important piece of security as well.

[koskimas]

You didn't answer my question at all.

[gdbjohnson]

@koskimas perhaps I'm not understanding what your question is. I've reread my question and I don't understand how it is unclear as to what I am trying to do.

In my project, we are following a convention that all tables have a field in them, a tenant ID. I want to use kysely to transform all queries being built to add a where condition. The challenge I am facing is that using expressionBuilder requires that I know the type of the query being transformed.

At the end of the day, kysely generates a string, and I just want to add "orgCode = 'XYZ'" in a where clause to all the queries. I would think a plugin is the natural way to do this.

Hope that clarifies?

[gdbjohnson]

Inside the plugin, I have access to the node hierachy created by kysely as it's parsing the query. I want to manipulate that tree by adding this where clause. So, I guess it's the query in the plugin?