Revert migration changes as domain expiry monitor is being removed
Co-authored-by: CommanderStorm <26258709+CommanderStorm@users.noreply.github.com>
This commit is contained in:
parent
4e28b99799
commit
b49c5aa463
@ -6,9 +6,7 @@ exports.up = function (knex) {
|
||||
.createTable("domain_expiry", (table) => {
|
||||
table.increments("id");
|
||||
table.datetime("last_check");
|
||||
// Use VARCHAR(255) for MySQL/MariaDB compatibility with unique constraint
|
||||
// Maximum domain name length is 253 characters (255 octets on the wire)
|
||||
table.string("domain", 255).unique().notNullable();
|
||||
table.text("domain").unique().notNullable();
|
||||
table.datetime("expiry");
|
||||
table.integer("last_expiry_notification_sent").defaultTo(null);
|
||||
});
|
||||
|
||||
@ -1,14 +0,0 @@
|
||||
// Ensure domain column is VARCHAR(255) across all database types.
|
||||
// This migration ensures MySQL, SQLite, and MariaDB have consistent column type,
|
||||
// even if a user installed 2.1.0-beta.0 or 2.1.0-beta.1 which had TEXT type for this column.
|
||||
// Maximum domain name length is 253 characters (255 octets on the wire).
|
||||
// Note: The unique constraint is already present from the original migration.
|
||||
exports.up = function (knex) {
|
||||
return knex.schema.alterTable("domain_expiry", function (table) {
|
||||
table.string("domain", 255).notNullable().alter();
|
||||
});
|
||||
};
|
||||
|
||||
exports.down = function (knex) {
|
||||
// No rollback needed - keeping VARCHAR(255) is the correct state
|
||||
};
|
||||
Loading…
Reference in New Issue
Block a user