riboseinc / container_record Goto Github PK

• We might want to also allow storing a Container's child tables in a separate database host
• Will want to keep a database connection pool (or reuse Rails' pool) but prime them prior to accessing Container child tables with (USE [container-database]).

And consider renaming this repo to replace the term Container ...

Each container should contain a schema_versions table, to record what migrations have been run within the Container.

For example, each of the N Company containers will have the same internal schema (say, files, messages).

When we want to migrate the files table across all company_* databases, the company_n/files table (located in the company_n database) is migrated from version X to X+1.

However, since migration of all company_n databases (from X to X+1) can be a lengthy process, we need to achieve zero-downtime with the container schema migrations.

This means that each company_1/files (e.g. version X+1) and company_2/files (e.g. version X) may be at different schema versions at any single time, and that the application should deal with this issue without hiccups.