Registry is at version 0 but latest is 1.1. Please run the "upgrade" conmand

[arnaldop]

I ran a command from shell history:

sqitch revert -y && sqitch --verbose deploy --mode change

I had just dropped all objects including the Sqitch schema, so the database was blank.

I sa #234 but my message is slightly different:

Registry is at version 0 but latest is 1.1. Please run the "upgrade" conmand

Please advise. For now the fix is to not run revert on an empty database.

Thanks!

[theory]

Are you using SQLite? If so, this commit might address the issue.

[arnaldop]

No, I'm on Postgres.
Thanks!

On Wed, Nov 18, 2015 at 11:48 AM, David E. Wheeler <notifications@github.com

wrote:

Are you using SQLite? If so, this commit
dcbbe6d
might address the issue.

—
Reply to this email directly or view it on GitHub
#271 (comment).

[theory]

This error happens when sqitch finds no registry schema objects. Without them, you cannot revert. Sqitch uses the registry to decide what to revert. Since you dropped them, it thinks that the registry is out-of-date. I'll improve it to detect when the registry simply isn't there. Meanwhile, to fix your issue, you'll have to revert all your changes yourself, or else drop the whole database and create a new one.

[arnaldop]

That's fine. I just figured the fix you just described would be a more
robust behavior for the app. I worked around it, though. Thanks again!

On Wed, Nov 18, 2015 at 2:26 PM, David E. Wheeler notifications@github.com
wrote:

This error happens when sqitch finds no registry schema objects. Without
them, you cannot revert. Sqitch uses the registry to decide what to revert.
Since you dropped them, it thinks that the registry is out-of-date. I'll
improve it to detect when the registry simply isn't there. Meanwhile, to
fix your issue, you'll have to revert all your changes yourself, or else
drop the whole database and create a new one.

—
Reply to this email directly or view it on GitHub
#271 (comment).

[EmilGerth]

This error also occurs if the account Sqitch is using does not have permission to the sqitch schema in Postgres (maybe others, too). Found this thread searching that error, and my solution ended up being those permissions. Important to note this error implies not having USAGE on sqitch - you will get a more specific "permission denied on relation" message if you are missing table access.

The quickest solution is to just make the account running your deployment owner of the database. ALTER DATABASE database OWNER TO role;

[theory]

Yeah, the Postgres user that runs Sqitch more or less needs admin access to the database. Owning the DB is the simplest way to do that, but if you use a single Sqitch user for a bunch of DBs on the same host, it's probably easiest to make that user a superuser. I tend to use a use other than postgres so that it's separate from other superuser use cases.