How to handle tables whose schema changes regularly?

[Jon Bowser (jbowser-bt)]

We're experimenting with DAB as a means of providing a no-code API for database tables and views. We have one view that regularly changes based on the dynamic nature of the data. When this happens, the API call fails due to "invalid columns" that no longer exist in the view. The only workaround I've found so far is to restart DAB.

How our others handling changing schema definitions?

[Sean Leonard (seantleonard)]

We have one view that regularly changes based on the dynamic nature of the data.

Sounds like the view schema changing frequently (new, removed columns). DAB doesn't auto detect this and requires a restart currently.

[Jon Bowser (jbowser-bt)]

I appreciate the response.

Do we know if support for this is on the roadmap?

[Sezal Chug (sezal98)]

Not currently, but we will check if we can prioritize this soon.
Resolving for now