Skip to content
This repository has been archived by the owner on May 15, 2024. It is now read-only.

Database format change causes relayer error #403

Closed
Amxx opened this issue Apr 4, 2019 · 1 comment
Closed

Database format change causes relayer error #403

Amxx opened this issue Apr 4, 2019 · 1 comment

Comments

@Amxx
Copy link
Collaborator

Amxx commented Apr 4, 2019

It looks like the pgsql format has changed recently. The database was initialized (on my machine) when I first started using the SDK about 1 month ago and everything was working well until recently.

Creating wallet worked well, but when I tryed to connect to an existing wallet, the new device got an error from the relayer:

error: "error: insert into \"authorisations\" (\"deviceInfo\", \"key\", \"walletContractAddress\") values ($1, $2, $3) returning \"id\" - la colonne « walletContractAddress » de la relation « authorisations » n'existe pas"

This is french for "column walletContractAddress of relation authorisations doesn't exist".

I managed to solve this by manually dropping the database. When I restarted the relayer I recreated it with the right format. Conclusion is, when starting a relayer, verifying that the database exist is not enough, it is also necessary to check it is in the right format.

@marekkirejczyk
Copy link
Contributor

Should be fixed #408

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants