Feature Request: making databasechangeloglock table functional

[dannov91]

databasechangeloglock table stores information that let us know whether a change set of migrations are running or not, that is to avoid race conditions if another dev tries to run migrations simultaneously.

When beginning any DB transaction, we should check if databasechangeloglock.locked column has a single value of true or false, and avoid any attempt of parallel migration runs.

Note: this is an example, I think this is somehow the behavior.

[paganotoni]

Thanks for bringing this topic in @dannov91. I wonder if we could research what the liquidase documentation says for this and maybe mimic it.

[paganotoni]

@dannov91 found these docs https://docs.liquibase.com/concepts/basic/databasechangeloglock-table.html on the implementation of the table.

[dannov91]

Really helpful! thanks you @paganotoni :)