System Architecture

Primary importance is placed on data integrity. The system is optimized for data integrity rather than maximal performance.[1]

The expectation is that the database will be read more often than written and is configured with that in mind.[2]

• Databases
  • sokwedb
  • sokwedb_test
  • sokwedb_dev
• Special Data Values
• Dates and Times
  • Input and Output Representations
  • Time Zones
• Database Permission Levels
  • Changing A User’s Permissions
  • The Administrator Permission Levels
• Logins
  • Administrators
  • Developers
  • Creating Logins
    • Creating Administrators
    • Creating Non-Administrative Logins
• Schemas
  • The sokwedb schema
  • The codes schema
  • The upload schema
  • The lib schema
  • The per-user private schemas

Footnotes

[1]

Among other choices of configuration, SokweDB ensures that concurrent database updates by different users will not lead to data inconsistency by setting the transaction isolation to serializable.

[2]

In particular, many indexes exist. This speeds query results but slows database writes.

Page last generated: 2026-03-15 23:16:59 UTC