Is there a hook/callback mechanism in terms of job status change

[xavierchow]

I have a use case that I need to handle some tasks(mostly DB writing) once a job is completed,
pushing the DB writing to the jobs leads too many DB connection so I'd like to have the main application to handle that part.

I'm wondering if sidequest has a mechanism to callback once the job has a status transition so the main app could have a chance to deal with something is not fit in the job run function.

thanks.

[GiovaniGuizzo]

@xavierchow unfortunately, no, Sidequest doesn't have this feature. You will need to poll the jobs statuses and do it manually.

[xavierchow]

@GiovaniGuizzo thanks for the quick response,
I looked into the code it seems I can leverage on the sidequest.job.list, underneath it uses sql-backend.listJob which works. However I'm using PostgreSQL and in my DB there are massive jobs, the supported queries are a bit slow without proper indexes.
do you think it's a good idea to add indexes for the out-of-box queries? maybe in migrations?

[GiovaniGuizzo]

Yes, it's possible. You can add more migrations yourself under @sidequest/postgres-backend or you can create those indexes directly on your DB as well.

However, I think it would be a cool idea to allow the user to provide custom indexes. Maybe I can come up with a solution in the next few days.

[GiovaniGuizzo]

After reading into this, I realized, we allow providing a Knex.Config object to the backend driver. You can setup custom Knex migrations there.

If you set your config.migrations.directory to an array of dirs, it will include all the migration files inside those dirs, so you can do something like this:

new PostgresBackend({
  connection: "postgresql://postgres:postgres@localhost:5432/postgres",
  migrations: {
    directory: ["node_modules/@sidequest/postgres-backend/migrations", "my/custom/migrations"],
  },
});

You will be able to include all the default Sidequest migrations + yours. Just make sure your migrations have the .cjs format.

Another possibility, if you are using yarn, is to use yarn patch. You can create patched migrations inside Sidequest's migrations dir directly without needing to reconfigure Sidequest with the aforementioned solution.