Table partitioning

Table partitioning is a division of one table into several tables, called partitions, which still represent original table. This is usually done for manageability, performance or availability reasons. If you are unsure whether you need partitioning or not, then you almost certainly don’t need it.

To use this feature, define the model as usual and create a table for it in the database using the usual tools that your ORM provides. After the table was created, this feature can be installed into the model as the following:

import architect

@architect.install('partition', **options)
class Model(object):

where options are:

  • type (required). Partition type, e.g. range, list etc
  • subtype (required). Partition subtype, e.g. date, integer etc
  • constraint (required). What data fits into partition, e.g. day, 5 (every 5 items) etc
  • column (required). Column, which value determines which partition record belongs to
  • db (optional). Currently used with:
    • Django - only for specifying other database name instead of default. Also if custom routers are used, Architect tries it’s best to figure out the database name from them automatically.
    • SQLAlchemy - required if model’s metadata is not bound to any engine, should be set in the form of DSN, e.g. dialect://user:pass@host/database.

Above options can take different values depending on the database type because different databases support different partition types, subtypes etc. To find out which values can be set for the above options choose the database type which you currently use from the list below:


Using this feature with a Django ORM, run the following command before moving to next step, substituting mysite.settings to the real path of the Django settings module:

$ export DJANGO_SETTINGS_MODULE=mysite.settings

After the feature has been installed into the model, run the following console command:

$ architect partition --module


You can optionally setup an AppConfig in Django to automatically run architect partition command after any migrations:

from architect.commands import partition

from django.apps import AppConfig
from django.db import ProgrammingError
from django.db.models.signals import post_migrate

def create_partitions(sender, **kwargs):
    After running migrations, go through each of the models
    in the app and ensure the partitions have been setup
    paths = {model.__module__ for model in sender.get_models()}
    for path in paths:
        except ProgrammingError:
            # Possibly because models were just un-migrated or
            # fields have been changed that effect Architect
            print "Unable to apply partitions for module '{}'".format(path)
            print "Applied partitions for module '{}'".format(path)

class DemoConfig(AppConfig):
    name = 'apps.demo'

    def ready(self):
        super(DemoConfig, self).ready()
        # Hook up Architect to the post migrations signal
        post_migrate.connect(create_partitions, sender=self)

That’s it. Now, when a new record will be inserted, a value from column, specified in the column option will be used to determine into what partition the data should be saved. Keep in mind that if new partitioned models are added or any settings are changed in existing partitioned models, the partition command should be rerun, otherwise the database won’t know about this changes.


After the installation partition feature can be accessed via Model.architect.partition, though it usually doesn’t need to be accessed directly because everything is done automatically. It provides the following methods:


Returns dictionary of model meta attributes needed for partitioning under common names.


Returns partition type object to work with depending on the given partition options.

This object provides the following methods:


Prepares everything that is needed to initialize partitioning.


Creates new partition.


Checks if partition exists.