Skip to content
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

booru_id is null #9

Open
thenamewastaken opened this issue Nov 24, 2019 · 0 comments
Open

booru_id is null #9

thenamewastaken opened this issue Nov 24, 2019 · 0 comments

Comments

@thenamewastaken
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant