DynamoDB doesn't have a concept of individual databases or name/key-spaces at the account level which means if you're running multiple applications on a single account then you need your own convention for defining table names. When using joplin.dynamodb, using a single 'migrations' clearly means that applications will interfere with one another so this PR introduces a mechanism by which the migrations table name can be specified; for example, app-a-migrations,app-b-migrations` etc.
DynamoDB doesn't have a concept of individual databases or name/key-spaces at the account level which means if you're running multiple applications on a single account then you need your own convention for defining table names. When using joplin.dynamodb, using a single 'migrations' clearly means that applications will interfere with one another so this PR introduces a mechanism by which the migrations table name can be specified; for example,
app-a-migrations,
app-b-migrations` etc.An example Joplin.edn 'database' field would be: