summaryrefslogtreecommitdiffstats
path: root/bin/db_legacy
Commit message (Collapse)AuthorAge
* Misc. code cleanupLibravatarJanik Kleinhoff2017-02-22
|
* DB: fix major fuckupLibravatarJanik Kleinhoff2017-02-13
| | | | | | | | | | | | | | | | | | | | | "id" in the alertlog table refers to the ID name of the alert rule that triggered, **not** to some sort of unique ID. This commit rewrites the database schema history used by DBIx::Class::DeploymentHandler as the previous schemata were utterly useless (and, in fact, seem to be undeployable). @Unit193, @Xenthys Clearly you managed to deploy a database somehow. If you used the legacy `DATABASE.SCHEMA` file and `bin/db_legacy`, you should be able to update via `bin/db_upgrade`; I've tested to verify this. (If you //haven't// run `db_legacy` yet, make sure to update to exactly de9f3deabe35, run `db_legacy`, then update to this commit and proceed with `db_upgrade`.) If you used the `db_deploy` script, may Cthulhu have mercy on your soul: I'm pretty sure that would not actually have worked. That said, it's my mistake, so if you require further assistance, feel free to poke me on freenode.
* Use DBIx::Class::DeploymentHandlerLibravatarJanik Kleinhoff2016-10-30
Fixes T5. Yay! We still need some documentation on this, though.