Is column based authorisation possible?
What about group/role based security concepts?
What about group/role based security concepts?
It' very similar to what we were doing with stored procs 15 years ago and just moves the problem from business logic back to database layer. Given the choice, I'd prefer to write constraints in !SQL, personally.
Yes.
> What about group/role based security concepts?
Yes, those have been standard in RDBMSs for decades.