Peer review of nested subqueries
My team is considering switching from Periscope (another BI system). One feature of theirs which we really like is their [Git integration](https://doc.periscopedata.com/article/git-integration#GitUseCases), which allows our team to manage changes to and history of charts and dashboards using pull requests via Github. We’d like to maintain a similar process on Metabase. FTR, we do have a team here and could potentially end up contributing this FR to the source code. The time cost of doing so would need to be weighed as one factor in our selection process, and we'd love to hear how this might be possible / how you'd prefer it added to your architecture (especially if you believe it's not unreasonable) to help us scope the work. (From discussion thread: https://discourse.metabase.com/t/peer-review-of-nested-subqueries/5359) :arrow_down: Please click the :+1: reaction instead of leaving a `+1` or `update?` comment
Posted by jfeldstein on Feb 7, 2019, 7:37 PM
Tags
Related issues
- >Beef is already too expensive for most people.
- I gave this a go a couple of years ago.
- I haven't seen any use cases around me, although I'm not that advanced user.
- [BUG] Pro Max 5x Quota Exhausted in 1.5 Hours Despite Moderate Usage
- > Unfortunately it doesn't offer free hosting for hobbyists.
- Still the same HID remapping project from last month (I was hoping to be done by now, but hardware is hard): https://github.co...
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
pricing (Software)
>Beef is already too expensive for most people.
I gave this a go a couple of years ago.
I haven't seen any use cases around me, although I'm not that advanced user.
[BUG] Pro Max 5x Quota Exhausted in 1.5 Hours Despite Moderate Usage
> Unfortunately it doesn't offer free hosting for hobbyists.
Still the same HID remapping project from last month (I was hoping to be done by now, but hardware is hard): https://github.co...
This criticism seems like a complete non-sequitur to me.
Bring back the GitHub Copilot in the CLI commands to not break workflows
Peer review of nested subqueries
My team is considering switching from Periscope (another BI system). One feature of theirs which we really like is their [Git integration](https://doc.periscopedata.com/article/git-integration#GitUseCases), which allows our team to manage changes to and history of charts and dashboards using pull requests via Github. We’d like to maintain a similar process on Metabase. FTR, we do have a team here and could potentially end up contributing this FR to the source code. The time cost of doing so would need to be weighed as one factor in our selection process, and we'd love to hear how this might be possible / how you'd prefer it added to your architecture (especially if you believe it's not unreasonable) to help us scope the work. (From discussion thread: https://discourse.metabase.com/t/peer-review-of-nested-subqueries/5359) :arrow_down: Please click the :+1: reaction instead of leaving a `+1` or `update?` comment
Comments (0)
No comments yet. Start the discussion.