# `mix pgflow.stamp`
[🔗](https://github.com/agoodway/pgflow/blob/v0.1.0/lib/mix/tasks/pgflow.stamp.ex#L1)

Marks an existing pgflow schema as installed under EctoEvolver's tracking
model without re-running V01 DDL.

Use when the pgflow schema already exists in the target database but is
missing the tracking comment on `pgflow.pgflow_version` — typical triggers:

  * Restored from a DB dump that lost object comments.
  * Schema was seeded manually via `psql` or another out-of-band path.
  * `PgFlow.Migration.up/0`'s preflight raised and pointed you here.

Writes the tracking comment only; runs no schema SQL. The next
`mix ecto.migrate` sees version 1 already applied and becomes a no-op.

**Destructive if schema drift exists.** If the installed schema diverges
from what `PgFlow.Migration` V01 would install, this task masks that
drift silently. Use only when you know the installed schema matches the
vendored V01 bundle.

## Usage

    mix pgflow.stamp
    mix pgflow.stamp --repo MyApp.OtherRepo --prefix custom_schema

## Options

  * `--repo` - Repo module to stamp (default: first in `:ecto_repos`).
  * `--prefix` - Schema prefix (default: `"pgflow"`).

---

*Consult [api-reference.md](api-reference.md) for complete listing*