Hi Gabriel My preferred way is to use the db features first, especially when you grant read, insert, update or delete (create a new user and grant what is allowed to him). But, if you have just one db user, which based on an application role has some rights (this is typically stored in an own table). You can use jOOQ’s VisitListener to check rights on your own “permission” table.
Regards, Thomas Am Sonntag, 21. Juni 2015 22:58:06 UTC+2 schrieb Gabriel Abadi: > > I've just read this amazing blog: > http://blog.jooq.org/2015/06/17/implementing-client-side-row-level-security-with-jooq/ > > I've some questions, if someone have a clue about how to implement that, > thanks in advance: > > There is something for, for example, limit user access to only read a > table (not save/update). Or a way to make a table completely inaccessible > for a user? > > Based on that article i belive that an exception could be thrown in the > filter if some invalid query is going to be executed. But i want to know if > that is the recomended way to do that. > > Thanks.. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
