Closed lathomas64 closed 2 years ago
I actually fixed this in 2b1001b2a5e871c7ba2afad89125c08b5a64f7de, making sure to hit every table -- there's some stuff involving time travel that isn't really exposed in the API and would be impractical to delete like this.
adding a change to sweep through the characters in the query if clear is true. If there are no characters this change should do nothing so it should be safe in that case.