- Expected cardinalities of tables in project life time:
Version: units
Objects: units of thousands
Property: tens of thousands
Translation: tens of thousands
Language: tens
User: tens to hundreds
- Access conflict resolution:
Resolution of conflicts is left on the database engine. From the nature of
the problem flows, that conflicts should be rare, because in most cases
users want to avoid of parallel work on same data object. Some objects can
be modified by one user only, so conflict should not occur. If some user
intentionally causes a conflict database engine should resolve it by
serialization of the access.
- Database access and consistency:
Users should not have a direct access to the database, all operations should
be carried out by SimuTranslator systems. Modules should allow only such
operations, which would lead to consistent state of the database.
- Accounts:
SimuTranslator will log to database using accounts appropriate for given
user type. Accounts for user types will have their rights restricted to
necessary operations only. (download account
descriptions) Access to the database will be only permitted from local
machine, no scripts running on other machines should be able to connect to
database.
- Data dictionary:
Data dictionary is described on data dictionary page.
|
