ALTER TABLE migration not running

[erayerdin]

My project structure is roughly like this:

...
migrations/V*_*.sql  # sql migrations
src/  # source files

And I use embedded migrations.

I have total of 9 migrations. Migrations that are related to the question are:

-- V3__create_posts_table.sql

CREATE TABLE posts (
    id SERIAL PRIMARY KEY,
    title VARCHAR(128) NOT NULL,
    content TEXT NOT NULL,
    due_date TIMESTAMPTZ NOT NULL,
    hide_post BOOLEAN NOT NULL,
    hint_title BOOLEAN NOT NULL,
    hint_tags BOOLEAN NOT NULL,
    hint_due_date BOOLEAN NOT NULL,
    hint_hash HINT_HASH_TYPE NOT NULL, -- custom type, ignore
    post_content TEXT NOT NULL,
    status STATUS_TYPE NOT NULL -- custom type, ignore
);

-- V8__create_users_table.sql

CREATE TABLE users (
    id SERIAL PRIMARY KEY,
    username VARCHAR(64) NOT NULL UNIQUE,
    password VARCHAR(64) NOT NULL,
    created_at TIMESTAMP NOT NULL
);

-- V9__add_user_id_to_posts_table.sql

ALTER TABLE posts
    ADD COLUMN user_id INTEGER REFERENCES users(id)
    ON DELETE CASCADE;

The program runs the first eight migrations but totally ignores the 9th migration. When I create a new fresh database, the logs are:

[INFO] refinery_core::traits schema history table is empty, going to apply all migrations
[INFO] refinery_core::traits::r#async applying migration: V1__create_hint_hash_type
[INFO] refinery_core::traits::r#async applying migration: V2__create_status_type
[INFO] refinery_core::traits::r#async applying migration: V3__create_posts_table
[INFO] refinery_core::traits::r#async applying migration: V4__create_post_histories_table
[INFO] refinery_core::traits::r#async applying migration: V5__create_tags_table
[INFO] refinery_core::traits::r#async applying migration: V6__create_posts_tags_table
[INFO] refinery_core::traits::r#async applying migration: V7__create_site_settings_table
[INFO] refinery_core::traits::r#async applying migration: V8__create_users_table
[INFO] rocket::launch 🔧 Configured for debug.
[INFO] rocket::launch_ address: 127.0.0.1
[INFO] rocket::launch_ port: 8000
[INFO] rocket::launch_ workers: 4
[INFO] rocket::launch_ ident: Rocket
[INFO] rocket::launch_ limits: bytes = 8KiB, data-form = 2MiB, file = 1MiB, form = 32KiB, json = 1MiB, msgpack = 1MiB, string = 8KiB
[INFO] rocket::launch_ temp dir: /tmp
[INFO] rocket::launch_ http/2: true
[INFO] rocket::launch_ keep-alive: 5s
[INFO] rocket::launch_ tls: disabled
[INFO] rocket::launch_ shutdown: ctrlc = true, force = true, signals = [SIGTERM], grace = 2s, mercy = 3s
[INFO] rocket::launch_ log level: normal
[INFO] rocket::launch_ cli colors: true
[INFO] rocket::launch 📬 Routes:
[INFO] rocket::launch_ (hello_world) GET /
[INFO] rocket::launch 📡 Fairings:
[INFO] rocket::launch_ Shield (liftoff, response, singleton)
[INFO] rocket::launch_ 'default_db' Database Pool (ignite)
[INFO] rocket::shield::shield 🛡️ Shield:
[INFO] _ Permissions-Policy: interest-cohort=()
[INFO] _ X-Frame-Options: SAMEORIGIN
[INFO] _ X-Content-Type-Options: nosniff
[INFO] rocket::launch 🚀 Rocket has launched from http://127.0.0.1:8000

Why does it not run?

---

Environment

• Rust 1.61.0
• Refinery 0.8.4 with tokio-postgres and postgres features
• PostgreSQL 12.11

[erayerdin]

Strangely, when I have moved embedded module somewhere else (thus causing Rust to recompile), it applied the migrations. So, it might be an idea to simply remove target directory and recompile the project again, I think?

[erayerdin]

Oh, yeah, now I think about it, that's the whole reason. I have added migrations, the migrations were embedded before. However, adding a new sql does not embed it into the program, so recompiling is the solution. Is there a way to do this without deleting target directory? Deleting target removes all compilation resources, causes waste of time waiting to compile.