Best Practises to handle database schema changes

Help me!
1

Feature(s) impacted

When database schema changes, not able to access the collection in forest

Observed behavior

I can resolve this issue by removing the error column from the codebase. However, we have multiple databases connected to the forest, which are used across the entire organization. When other teams modify a table schema (e.g., removing columns), we don’t receive any notifications. As a result, the forest throws an error when attempting to access the missing column.

Expected behavior

Is there any best practices to avoid this kind of behavior in forest. Basically, ia m looking for an alternative to avoid these kind of errors.

Failure Logs

{
“errors”: [
{
“status”: 500,
“detail”: “Unknown column ‘schedules.source’ in ‘field list’”,
“name”: “SequelizeDatabaseError”
}
]
}

Context

  • Project name: …
  • Team name: …
  • Environment name: dev, staging and production
  • Agent technology: nodejs
  • Agent (forest package) name & version: …
  • Database type: Mysql
  • Recent changes made on your end if any: …
2

Hello @Sudheer_K,

You have to find a way to release the agent with the correct schema whenever you update your database schema. There is no alternative way as in configuration to support a missing field from your database.