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

Allow value lists/arrays as property values #46

Open
mwahle opened this issue Oct 23, 2018 · 3 comments
Open

Allow value lists/arrays as property values #46

mwahle opened this issue Oct 23, 2018 · 3 comments
Labels
Enhancement New features or upgrades for functionality, performance, etc Priority: Backlog Tasks that are not pressing, but to be tracked and revisited

Comments

@mwahle
Copy link

mwahle commented Oct 23, 2018

We are developing a tagging application. Instances can be tagged with one or more values. Currently one has to apply workarounds, like concatenating strings, using blobs, or power-of-two integers and doing interpretation work on the application side to be able to save more than one value to a property. This introduces unnecessary complexities and conventions into the code and is not a very robust way of handling this.

Please add this capability to VDMS.

New operator semantics for the constraints block would be useful. One would need to be able to indicate that the given search value(s) should be contained in the list of values on the property or match exactly the entire list of values in the property.

For example, "constraints": { "tag": [ "<=", [ "valueA" ] ] } to match all properties with a value list that contain at least "valueA". Or "constraints": { "tag": [ "==", ["valueA", "valueB" ] ] } to match all properties that have exactly this value list.

@luisremis luisremis self-assigned this Oct 23, 2018
@luisremis luisremis added the Enhancement New features or upgrades for functionality, performance, etc label Oct 23, 2018
@vishakha041
Copy link
Contributor

<= and == currently exist to mean strings that will lexicographically are less than and equal to or equal to (that should work already if that's what you mean). For the list of values, we could add new operator keywords like "in". I think we might have something similar to this in progress already.

@mwahle
Copy link
Author

mwahle commented Oct 24, 2018

I liked the idea of overloading <= and == but of course that may not be up to everybody's taste. May I suggest to use the in keyword for actual "in queries" (like the SQL in operator). Of course it could also be overloaded for single-value properties and multi-value properties...

PS. I am aware you already implemented "in queries" with another operator but I think it would be better to use in as keyword.

Ragaad pushed a commit to Ragaad/vdms that referenced this issue Jun 16, 2022
* Resolve the memory issue on video ops

* Fix bugs on exception handling
@ifadams
Copy link
Contributor

ifadams commented Jul 23, 2024

@cwlacewe reasonable request, though probably low-priority at the current time.

@ifadams ifadams added the Priority: Backlog Tasks that are not pressing, but to be tracked and revisited label Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New features or upgrades for functionality, performance, etc Priority: Backlog Tasks that are not pressing, but to be tracked and revisited
Projects
None yet
Development

No branches or pull requests

4 participants