-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
value for domain lovelace violates check constraint "lovelace_check" #351
Comments
😢 Yeah, this is disappointing. It looks like Dropping that |
It seems the ledger accepts nonsensical values for 'pool_update.fixed_cost' like a value greater than max Lovelace. That means we need to handle it too :-(. Closes: #351
Now we get a warning:
and |
It seems the ledger accepts nonsensical values for 'pool_update.fixed_cost' like a value greater than max Lovelace. That means we need to handle it too 😢. Closes: #351
This is a workaround fix for: #351 This fix will not require the database to be re-synced, but will result in some bad values being display as negative value.
This is a workaround fix for: #351 This fix will not require the database to be re-synced, but will result in some bad values being display as negative value.
This is a workaround fix for: #351 This fix will not require the database to be re-synced, but will result in some bad values being display as negative value. Also includes a fix for the first stage of the schema migrations.
This is a workaround fix for: #351 This fix will not require the database to be re-synced, but will result in some bad values being display as negative value. Also includes a fix for the first stage of the schema migrations.
This is a workaround fix for: #351 This fix will not require the database to be re-synced, but will result in some bad values being display as negative value. Also includes a fix for the first stage of the schema migrations.
This is a workaround fix for: #351 This fix will not require the database to be re-synced, but will result in some invalid values for the 'fixed_cost' field of the 'pool_update' table being display as negative value. The constraint will be droppped only if it exists (eg someone had previously dropped in manually).
On the mainnet, just after slot height 4830407, cardano-db-sync is stuck with following:
As a workaround, removing the constraint check seems to be a workaround, however, I'm sure it was in place for a good reason.
psql> ALTER DOMAIN lovelace DROP CONSTRAINT lovelace_check;
The text was updated successfully, but these errors were encountered: