We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some customers define the same expression in many queries, either as HogQL expressions in trends or as part of a HogQL query.
It'd be cool if they could add them as a virtual property (similar to the experimental $virt_initial_channel_type on the persons model).
We'd need to make sure the property works in a few different scopes, e.g.
select persons.$my_virtual_property from persons; select events.person.$my_virtual_property from events;
A lot of copy/pasting ;)
It came up in this Zendesk ticket https://posthoghelp.zendesk.com/agent/tickets/22482
It'd be cool if this column could be used in batch exports too, it'd be a way for customers to add computed fields to that.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Feature request
Is your feature request related to a problem?
Some customers define the same expression in many queries, either as HogQL expressions in trends or as part of a HogQL query.
Describe the solution you'd like
It'd be cool if they could add them as a virtual property (similar to the experimental $virt_initial_channel_type on the persons model).
We'd need to make sure the property works in a few different scopes, e.g.
Describe alternatives you've considered
A lot of copy/pasting ;)
Additional context
It came up in this Zendesk ticket https://posthoghelp.zendesk.com/agent/tickets/22482
It'd be cool if this column could be used in batch exports too, it'd be a way for customers to add computed fields to that.
The text was updated successfully, but these errors were encountered: