1, why must the module name have @ prefix?
Because in order to unify the module's method, if has the module name prefix is @, then the system will go to the system comes with the own internal Database (AM.dat) in
Get the configuration information for the module.
So in order to distinguish it from other standard modules, the module name must use the prefix name @
2, in the internal database AM.dat, need a special name?
should not be needed.
There should be mainly these tables: Modulefields
Modulerelations
So no special naming is required.
3, in the system database, System.dat or Mysql,mssql database, and permissions-related tables, need to add special prefixes?
It should be said that since this table is used by the system itself, it should be considered that it does not matter whether or not to use prefixes.
The base table is as follows:
and permissions related to the following
Users
Roles
User_role
User_module, wait.
and modules related to the following
Modulegroup
Moduledefields
Modulerelations, wait.
Logically, there is no need for additional data tables in this library.
In this sense, no additional identification is required
4. Conclusion
You only need to add the @ symbol to the module name before the module is named, and the permission module is identified.
For example, @user actually refers to the user table in System.db.