在私有内部内中,考虑用包访问权限替代私有访问权限。
Consider Package Instead of Private Access with Private Inner classes.
如果你在高性能的Hotspot中使用这些代码,可以通过声明被内部类访问的字段和成员为包访问权限,而非私有。
If you're using code like this in a performance hotspot, you can avoid the overhead by declaring fields and methods accessed by inner classes to have package access, rather than private access.
所有内容(报告、分析、文件夹、包等等)以及许多函数和系统功能都可以有相关联的权限(例如对Studios的访问权)。
All content (reports, analysis, folders, packages, and so on) and a wide range of functions and capabilities of systems can have permissions attached to them (for example, access to Studios).
换句话说,如果对某个表的所有访问都是静态的,则DBA将不需要授予对整个表或视图的访问权限,而是仅授予对包的访问权限。
In other words, if all access to a table is static, the DBA would not need to grant access to the entire table or view, just to the package.
当您被授予使用一个视图或包的权限时,您被自动获得对视图或包中各个表的访问权限。
When you are granted privileges to use a view or a package, you automatically get access to the tables referenced in the view or package.
最后,您可能想要控制并授予特定用户访问数据包的特定权限。
Finally, you might want to control and grant the privileges to specific users to provide specific access to the packages.
我们已经确保了访问数据的安全性,但在授予用户访问数据的权限,而黑客却能够访问通过Internet传输的数据包时,会出现什么情况呢?
We have secured access to the data, but what happens when a user is given access to the data, and a hacker can access the data packets as they are being sent across the Internet?
我们已经确保了访问数据的安全性,但在授予用户访问数据的权限,而黑客却能够访问通过Internet传输的数据包时,会出现什么情况呢?
We have secured access to the data, but what happens when a user is given access to the data, and a hacker can access the data packets as they are being sent across the Internet?
应用推荐