open-source-mirrors
/
bazarr
mirror of https://github.com/morpheus65535/bazarr
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c97a98d4f2'
${ noResults }
bazarr/libs/alembic/templates/multidb
History
morpheus65535 bccded275c
Replaced peewee with sqlalchemy as ORM. This is a major change, please report related issues on Discord. 		1 year ago
..
README Replaced peewee with sqlalchemy as ORM. This is a major change, please report related issues on Discord. 1 year ago
alembic.ini.mako Replaced peewee with sqlalchemy as ORM. This is a major change, please report related issues on Discord. 1 year ago
env.py Replaced peewee with sqlalchemy as ORM. This is a major change, please report related issues on Discord. 1 year ago
script.py.mako Replaced peewee with sqlalchemy as ORM. This is a major change, please report related issues on Discord. 1 year ago

README 

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.