Geir Ove Grønmo
- Total activity 30
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 15
Activity overview
Latest activity by Geir Ove Grønmo-
Geir Ove Grønmo commented,
Official comment Introducing grouping to the list view is something we want to avoid. Is it specifically the direction you are missing? If so, we can add that as a column so you can sort on it.
-
Geir Ove Grønmo commented,
Official comment We'll try to implement this, but we somewhat bound to the limits of the editor we use.
-
Geir Ove Grønmo commented,
Official comment In general we want the pipe to be self-contained. We do not want to introduce the complexity of maintain external logic outside of the pipe itself at this time. It would require a policy for how to...
-
Geir Ove Grønmo commented,
Official comment What is the use-case you want to use it for?
-
Geir Ove Grønmo commented,
Official comment We recommend that you always write to a table that you fully own. You then use db functions like triggers to merge the values you want.
-
Geir Ove Grønmo commented,
Official comment There is already an undocumented DTL function that lets you do this. We have not yet had any request for this function, but now that you need it can make it official by documenting it. ["fail!",...
-
Geir Ove Grønmo commented,
Official comment If you mean the VPN between Sesam and the customer side then this is a somewhat customer specific solution at the moment. We understand the requirement, but we are working on standardising this int...
-
Geir Ove Grønmo commented,
Official comment We are working on unifying how users download and view that data in their browsers.
-
Geir Ove Grønmo commented,
Official comment Use the "Show flows" button on the pipe page (top right) to get a better overview of the flows. We're working on creating better visualization tools for showing the complete input to output flow fo...
-
Geir Ove Grønmo commented,
Official comment Performance in the freetext search is by design limited. The cost of putting a dedicated search engine on top of a dataset is not prioritized.