LucidDB, and CUBRID, users code functions and procedures in Java. Note (3): ENUM datatype exists. CHECK clause is parsed, but not enforced in runtime. Note (5): Informix supports external functions written in Java, C, & C++. Partitioning Information about what partitioning methods are supported natively. Note (1): Raima Database Manager 14.0 requires the application programs to select the correct partition (using range, hash or composite techniques) when adding data, but the database union functionality allows all partitions to be read as a single database. Access control Information about access control functionalities. Note (1): Network traffic could be transmitted in a secure way (not clear-text, in general SSL encryption). Precise if option is default, included option or an extra modules to buy. Note (2): Options are present to set a minimum size for password, respect complexity like presence of numbers or special characters. Note (3): How do you get security updates? Is it free access, do you need a login or to pay? Is there easy access through a Web/FTP portal or RSS feed or only through offline access (mail CD-ROM, phone). Note (4): Does database process run as root/administrator or unprivileged user? What is default configuration? Note (5): Is there a separate user to manage special operation like backup (only dump/restore permissions), security officer (audit), administrator (add user/create database), etc.? Is it default or optional? Note (6): Common Criteria certified product list. Note (7): FirebirdSQL seems to only have SYSDBA user and DB owner. There are no separate roles for backup operator and security administrator. Note (8): User can define a dedicated backup user but nothing particular in default install. Note (9): Authentication methods. Note (10): Informix Dynamic Server supports PAM and other configurable authentication. By default uses OS authentication. Note (11): Authentication methods. Note (12): With the use of Pervasive AuditMaster. Note (13): User-based security is optional in Polyhedra, but when enabled can be enhanced to a role-based model with auditing. Databases vs schemas (terminology) The SQL specification defines what an "SQL schema" is; however, databases implement it differently. To compound this confusion the functionality can overlap with that of a parent database. An SQL schema is simply a namespace within a database; things within this namespace are addressed using the member operator dot ".". This seems to be a universal among all of the implementations. A true fully (database, schema, and table) qualified query is exemplified as such: