Thank you for sharing your idea with us. After evaluating this suggestion, we will not be implementing the feature to enable direct column modifications in the internal drillthrough database. However, as an alternative, we recommend using a self-managed PostgreSQL or SQLite database to retain full control over columns, data, and tables, similar to what you previously had with an on-prem setup. This approach provides greater flexibility than our internal database, which, by design, limits certain management functions.
Hi there,
The status was for internal feedback gathering.
After discussions with devs since we cannot commit to the new feature we come up with some alternatives:
One possible solution is transitioning to a customer-managed database and connecting it to the persisted drillthrough.
While we do offer a database as a service, it's not necessary for this approach.
If you opt for an external PostgreSQL database, you may have slightly less control than with your own managed database, but you’ll still have access to all the essential features.
The concern about "native functionalities being limited" doesn't apply here, as a self-managed database gives you full control.
You could also consider SQLite as an option for managing drillthrough data.
Lastly, the limited control we mentioned earlier refers specifically to our internal drillthrough database—while we can enhance it with certain features, it likely won’t offer the same level of control you had with the on-prem setup.
you changed to status "needs feedback", what feedback do you need?