objection.js | An SQL-friendly ORM for Node.js | SQL Database library

I used Objection.js as ORM for my Nest.js app. I tried to implement global error handling for both Http exception and Objection Error (ORM / Database Error). Suppose I make a mistake inserting a same unique value, it would throw UniqueViolationError. But every time I throw error on the users.service.ts (users module service) part of the app, on the service the error still an instance of UniqueViolationError but on filters it became the instance of HttpExceptionError thus my filters won't work. Here is the full code :

errors.filters.ts

I have four tables vehicle_parts, part_pricing, labour_pricing and paint_pricing. Vehicle_parts table is having one to many relationship with remaining tables. Each table is having a field is_active indicating whether record is active or not. So ideally for every part in vehicle_parts table there will be only one active price in part_pricing.

I am using Objection.js to build my model as shown below -

I have a function where i am querying the vehicle part model to fetch vehicle parts along with associated prices, as shown below -

I am using withGraphFetched() method to get relational data and i am getting that.

The problem i am facing is when i am getting vehicle parts, i am getting active parts only, however i am getting non-active prices as well along with active price in relational data. I know this can be solved using modifiers but i am not sure how to use that. In simple words i need to check is_Active flag in every relation when fetching data using withGraphFetched().

Thanks for sharing your wisdom.

I would like to create an expired_bool virtual column.

I have the following 3 tables:

subscriptions:

invoices:

invoice_items:

This is how the User, Invoice, and InvoiceItems tables are modeled in Objection.js:

I'm evaluating Node.js 14.x for a new project. I'm testing Knex.js and Objection.js to interact with databases so I'm building a proof-of-concept project, but I'm running into some issues when trying to run the migrations (using npx knex --esm migrate:latest):

I'm trying to relate two models with an extra property of "url":

I am using objection.js, and I have this model, and would like to get other object instances that share the same property value as the current instance, e.g.

I want to insert a data into my database based on "where" condition, but I couldn't success.

Objection.js :

I am creating Express API and I am using Objection.js as ORM with Knex.js I have created router for updating user password from the profile with 2 fields (old password and the new password),first it verifies the old password (protection from stealing JWT token). After it returns valid condition then I proceed to hash the new password with bcrypt and update it with .patch() otherwise it will return validation error the old password it is not the correct password. The problem is when I send the same exact request it goes through meaning that .patch not worked and did not save the new password to the database. Can anyone explain some solution to this problem or probably hit me with some documention on how to fix it The code is bellow:

I'm looking for a way to capture the raw SQL for all the queries that the Objection.js library executes with the bindings interpolated into the SQL string.

I realize that there's a Knex event handler that I can take advantage of but the second argument to the on('query', data) is an object containing an SQL template with the bindings separate.

e.g.