S
Stefan Marquardt
Guest
It's painful that I can't access tables for SQL only from the ABL. Currently I need to grant or revoke rights on tables for many users. I like to have an ABL program to set them but this is not possible. The solution is to create an input file for sqlexp and run it. But the performance to set the rights for all tables for all existing users (read only or not) is very poor. And on the top during the execution of the sqlexp the schema is locked very often and ABL users are getting a schema locked error during the try to login (connect). Sorry - but this may not happen that an sql command blocks ABL users! And on the top I am missing more general Rules in the sql access, like DataReader, this would reduce the amount of command for sqlexp. If I can't access SQL rights from ABL why SQL is blocking ABL the other way around? This isn't a question, this is a design error - my opinion. Try it on your own, take every user from _user and create a revoke select command for every table. (I have <500 tables and ~ 500 users) The result is a very long running sqlexp and during this time schema locks. (revoke select on PUB."Table" from "USER" ;
Continue reading...
Continue reading...