sqitch-check(3pm)

💖 sqitch-check 💖

okay so bestie, buckle up, because this is the page for sqitch-check from the User Contributed Perl Documentation, and it's literally the vibe-check command for your database. It 👏 checks 👏 for divergences between planned and deployed changes. no cap.

---

✨ SYNOPSIS ✨

sqitch check [options] [<database>]

---

🌸 DESCRIPTION 🌸

So what does it actually do? It compares the state of the working directory and the database by comparing the SHA1 hashes of the deploy scripts. iykyk, that's the receipts.

If any change has a non-matching hash, it fails and reports divergence for all of them — because that means your project deploy scripts are not the same scripts that were used to deploy to the database. it's giving "who are you and why do you look different 🫣".

The <database> parameter tells it which database to connect to, and you can also pass that as the --target option instead. It can be a target name, a URI, an engine name, or a plan file path. flexible queen 💅

---

👑 OPTIONS 👑

• -t, --target — the target database to which to connect. This option can be either a URI or the name of a target in the configuration.
• --project — the project for which to retrieve the status. Defaults to the status of the current project, if a plan can be found.
• --registry — the name of the Sqitch registry schema or database in which sqitch stores its own data. like, where it keeps its own diary.

sqitch check --registry registry

• --db-client, --client — path to the command-line client for the database engine. Defaults to a client in the current path named appropriately for the database engine. it'll go find its own little guy if you don't point at one.

sqitch check --client /usr/local/pgsql/bin/psql

• -d, --db-name — name of the database. In general, targets and URIs are preferred, but this option can be used to override the database name in a target. override era fr fr.

sqitch check --db-name widgets
sqitch check -d bricolage

• -u, --db-user, --db-username — user name to use when connecting to the database. Does not apply to all engines. In general, targets and URIs are preferred, but this option can be used to override the user name in a target.

sqitch check --db-username root
sqitch check --db-user postgres
sqitch check -u Mom

• -h, --db-host — host name to use when connecting to the database. Does not apply to all engines. In general, targets and URIs are preferred, but this option can be used to override the host name in a target.

sqitch check --db-host db.example.com
sqitch check -h appdb.example.net

• -p, --db-port — port number to connect to. Does not apply to all engines. In general, targets and URIs are preferred, but this option can be used to override the port in a target.

sqitch check --db-port 7654
sqitch check -p 5431

• --plan-file, -f — path to the deployment plan file. Overrides target, engine, and core configuration values. Defaults to $top_dir/sqitch.plan. she said "I have my own plan and it overrides everything 💅".

sqitch check --plan-file my.plan

---

🦋 SQITCH 🦋

Part of the sqitch suite. one big happy family 🫶

---

okay that's the whole page bestie, you ate it up 💖 this was sqitch-check(3pm) from perl v5.40.1, dated 2026-07-26, and it lives in the User Contributed Perl Documentation. mwah, go check your hashes, ily ✨🎀