NI'm surprised that it's trying to run migration. You should have an lldap_metadata column with the version number which should be 8+ (don't remember the exact value)
N(after just creating the schema)
NThat's weird, creating the schema should have set the version number. Did you get any error when creating the schema?
NThe scripts are written in rust, because they get translated to the DB specific dialect
NI'd have to maintain 3 different sets of migration scripts, including migration logic
NI wouldn't want to have to translate the migrations into a different format, that seems risky.
Why is running the migrations as part of LLDAP startup a problem?
Why is running the migrations as part of LLDAP startup a problem?
NIt sounds like you can have a simple flyway migration that just creates an empty DB, and let LLDAP populate it on first run (you don't need to create the schema in advance)
NOr if you want pre-existing data in the DB, then it should already be pre-migrated and it's just a matter of copying it to the new DB, which is not a migration?
N(sorry if I don't understand your workflow)
NYes it will!
NThat's why the migration scripts are in Rust, they're made to handle all 3 DBs
NGreat 
NHave another look at the place where the docs were confusing, and if you can propose a clarification, it'll be gladly accepted!