You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding a comment to an adlist that contains a quote mark or apostrophe, i.e. "Person**'**s Blocklist", breaks the gravity update on the "pull" client after the database update.
After updating the database, the pull client attempts a gravity update and receives an error: [i] Creating new gravity databases... [✗] Unable to copy data from /etc/pihole/gravity.db to /etc/pihole/gravity.db_temp Runtime error near line 24: FOREIGN KEY constraint failed (19) [✗] Unable to create gravity database. Please try again later. If the problem persists, please contact support.
Removing the quote marks from blocklist comments on the "push" client allows the "pull" client to update gravity correctly after the next pull.
Examining the db_dump.sql file shows that the insert command attempts to escape the single quote by doubling it. This appears not to be handled well on the other end.
The text was updated successfully, but these errors were encountered:
hartacus
changed the title
Adlist comment with quotemark breaks gravity update after "pull"
Adlist comment with quotemark breaks gravity update after pull
Dec 3, 2023
Adding a comment to an adlist that contains a quote mark or apostrophe, i.e. "Person**'**s Blocklist", breaks the gravity update on the "pull" client after the database update.
After updating the database, the pull client attempts a gravity update and receives an error:
[i] Creating new gravity databases... [✗] Unable to copy data from /etc/pihole/gravity.db to /etc/pihole/gravity.db_temp Runtime error near line 24: FOREIGN KEY constraint failed (19) [✗] Unable to create gravity database. Please try again later. If the problem persists, please contact support.
Removing the quote marks from blocklist comments on the "push" client allows the "pull" client to update gravity correctly after the next pull.
Examining the db_dump.sql file shows that the insert command attempts to escape the single quote by doubling it. This appears not to be handled well on the other end.
The text was updated successfully, but these errors were encountered: