-
Notifications
You must be signed in to change notification settings - Fork 56
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
Child curations - backend. #321
base: develop
Are you sure you want to change the base?
Child curations - backend. #321
Conversation
…children, fix a few typos, and a few small bugfixes.
I was getting meh performance with sqlite3, and I heard better-sqlite3 was faster. It seems to be so.
Pull Request Test Coverage Report for Build 2234249069
💛 - Coveralls |
Things I currently know that I need to fix:
|
That is: I hope so. I haven't tested curation yet, but I *think* this will fix some portions of it.
Previously, the blank platform strings of children were included in the results of findPlatforms().
Also make some == into ===, and make the message bar appear in when browsing.
In case you're wondering about the point of b49d9c1: in my testing, it looked like |
|
This reverts commit c64d1f7.
Remove some temporary statements, and add a relation-loading statement for the tags of child games.
Previously, the param was marked as optional. However, failure to supply it resulted in an error (column not found).
Switch the comparison for keyset pagination when orderBy is different.
Don't open a new database connection if one already exists, and don't close the connection at the end of testing.
Also: add some jsdoc and a possible todo, and remove an unneeded selected colum.
Also switch filtering funcs to === from ==.
Also clean up some TODOs.
Implement the child edit function and turn on cascades for children. Set the default child modified and added dates to the unix epoch. Previously, the all-zeroes date was resulting in a null datetime object.
Also remove some todos.
That should bring it up to date with develop. The GameManager tests are in the wrong place though, one moment. |
The backend changes for #245.
Also, switch toNope,better-sqlite3
: performance was suffering without it, and I can't see a reason to stick with a slower version of the same functionality.better-sqlite3
doesn't do migrations correctly. It's been reverted.For the testing: I've begun with rewriting the tests for
GameManager.ts
. I'm not too clear on how to test things beyond that... we'll see.