pull down to refresh
reply
Thank you sir
reply
reply
I changed it myself in the process of figuring out what was going on. Hopefully ~charts_and_maps is what you intended?
The root cause is that the name update conflicts with the periodic (and frequent) aggregates we compute. I had to disable those aggregates to prevent the error, because the real fix is going to be invasive and I didn't want to leave you hanging.
I'll try to get the real fix in by the end of the weekend.
reply
Yes, perfect, thank you!!
reply
https://media.tenor.com/eDjkZ-51FzsAAAAM/well-this-is.gif
@k00b I getting some errors when trying to change territory names:
Invalid
prisma.sub.update()invocation: Error occurred during query execution: ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(PostgresError { code: "40P01", message: "deadlock detected", severity: "ERROR", detail: Some("Process 1385 waits for ShareLock on transaction 3982037312; blocked by process 22193.\nProcess 22193 waits for ShareLock on transaction 3982037086; blocked by process 1385."), column: None, hint: Some("See server log for query details.") }), transient: false })Invalid
prisma.sub.findUnique()invocation: Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 2)