Skip to content
New issue

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

Improve support for arrays, including ANY(), ALL() and UNNEST() #178

Open
dnicolodi opened this issue Jun 15, 2024 · 0 comments
Open

Improve support for arrays, including ANY(), ALL() and UNNEST() #178

dnicolodi opened this issue Jun 15, 2024 · 0 comments
Labels
feature New feature

Comments

@dnicolodi
Copy link
Collaborator

There is already very minimal support: tags and links are exposed as columns of type set and there are the IN and NOT IN operators. This needs to be expanded to at least include the ANY() and ALL() operators. This most likely needs support from the parser.

The type system needs to be expanded to take into consideration the type of the elements of a set or array. It makes sense to enforce that all the elements of a set or array have the same type. Use a syntax similar to the Postgresql one: type[] to indicate an array of element of type type. Maybe it is not necessary to distinguish between sets and arrays at the type system level. However, Python sets are not indexable.

Once this is done, the other_accounts in the postings table can be replaced by adding an accounts str[] fields to the entry type and usage of other_accounts can be replaced with entry.accounts.

@dnicolodi dnicolodi added the feature New feature label Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

No branches or pull requests

1 participant