When I create a post or a pool, the operation is successful but Archives' database is not updated due to the "booru_id" column being null.
I should probably specify that I'm using Archives without AWS, after I substituted the cloud service with a local service reading from a UNIX socket (it's just a ruby server with two threads writing to and reading from a shared Queue object.)
Despite that radical, the data is sent correctly to Archives from the main Danbooru and in fact inspecting it I could see that all the expected fields are there with a value, except "booru_id" which is missing from the JSON and thus null.
I solved this by creating a new migration dropping the "booru_id" column, but I don't know if this is the correct solution.
When I create a post or a pool, the operation is successful but Archives' database is not updated due to the "booru_id" column being null. I should probably specify that I'm using Archives without AWS, after I substituted the cloud service with a local service reading from a UNIX socket (it's just a ruby server with two threads writing to and reading from a shared Queue object.) Despite that radical, the data is sent correctly to Archives from the main Danbooru and in fact inspecting it I could see that all the expected fields are there with a value, except "booru_id" which is missing from the JSON and thus null. I solved this by creating a new migration dropping the "booru_id" column, but I don't know if this is the correct solution.