SQL databases

Dari supports MySQL, PostgreSQL, and Oracle, all of which are implemented using the same underlying table structure and indexing strategy. Dari’s SQL database schema is implemented using multiple tables (see below). The primary table, Record, stores the raw information about the objects that are saved. Objects are serialized to JSON format when they are saved and stored in the data column of the Record table. Several other tables are used to implement field indexes.

Dari creates unique IDs for every object by generating a UUID. The id and typeId fields in the Record table store these UUIDs in the most appropriate datatype for the underlying database. For MySQL and Oracle, this is binary(16). On PostgreSQL, the native UUID is used.

Because SQL databases generally provide fast primary key lookups, Brightspot projects typically use an SQL implementation as the primary database. However, SQL database performance is limited for text matching and compound-predicate queries. Therefore, Brightspot projects generally supplement the SQL implementation with the Solr database, which Dari uses for full-text searches.

See also:

• Indexes
• Debugging with Dari

Dari implements indexing using four primary index tables: RecordString, RecordNumber, RecordUuid, and RecordLocation.

When fields of an object are indexed, the field’s value along with its object ID are stored in the appropriate index table.

The following table lists the tables that Dari creates in SQL-based databases. An integer in the table name indicates a version, which may be different in your database.