-
Notifications
You must be signed in to change notification settings - Fork 7
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
deps: RN-1112: bump knex
to 3.1.0
#5483
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be alright for me to ask you to look into exactly what's going wrong with the failing test in the @tupaia/database
package when we upgrade it?
It looks like once again it's related to jsonb operators (we use them in the dashboard_relation.entity_attributes_filter functionality). If it's possible for us to find out how to get that working on the latest version of knex I'd love if we could upgrade globally 👍
Co-authored-by: Rohan Port <59544282+rohan-bes@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work, thanks for persevering through this 💪
You might need to rebase to get the github actions to pass?
# Conflicts: # packages/data-lake-api/package.json # packages/database/package.json # packages/types/package.json # yarn.lock
Issue RN-1112: Bump
knex
to 3.1.0Changes
@tupaia/database
’sgetColSelector()
currently produces->
and->>
JSON selectors in its output, but for some reason this breaks with newer versions of Knex where positional parameters get out of order and messes up queries. I’ve fixed this by makinggetColSelector()
construct equivalent queries using#>>
, but usage of the function remains the same. It should continue to be provided input strings with->
and->>
.