Christopher Kings-Lynne wrote:
I think column privileges is orthogonal to this issue. The ability to "protect" stored procedure or package source is common among at least the commercial databases I've worked with (as is column level grants).I think this would be a good idea, though there becomes a question of what type of performance hit comes into play when doing this. I suppose if you have an option whether to encrypt it or not that would help. One other thing is that it needs to be "decryptable" by owners and superusers.Surely a more generic column privileges implementation would be better?
Joe
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
