Current Path: > > opt > hc_python > lib > python3.12 > site-packages > alembic > templates > > multidb
Operation : Linux premium131.web-hosting.com 4.18.0-553.44.1.lve.el8.x86_64 #1 SMP Thu Mar 13 14:29:12 UTC 2025 x86_64 Software : Apache Server IP : 162.0.232.56 | Your IP: 216.73.216.111 Domains : 1034 Domain(s) Permission : [ 0755 ]
| Name | Type | Size | Last Modified | Actions |
|---|---|---|---|---|
| __pycache__ | Directory | - | - | |
| README | File | 606 bytes | April 04 2025 08:02:35. | |
| alembic.ini.mako | File | 3866 bytes | April 04 2025 08:02:35. | |
| env.py | File | 4230 bytes | April 04 2025 08:02:35. | |
| script.py.mako | File | 1220 bytes | April 04 2025 08:02:35. |
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.
SILENT KILLER Tool