Bug 1112646 - [RFE] LVM selection criteria - add support for selection criteria shortcuts
Summary: [RFE] LVM selection criteria - add support for selection criteria shortcuts
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: lvm2
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Peter Rajnoha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-24 12:00 UTC by Peter Rajnoha
Modified: 2024-08-12 10:34 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-08-12 10:34:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Peter Rajnoha 2014-06-24 12:00:45 UTC
(from bug #867376 comment #8)

Another extensions may include shortcuts like:

'lvs --select name=[a || b || c]' which would be equal to 'lvs --select name=a || name=b || name=c' (this should be easy to add).

If found usable for some situations, maybe also transitive comparisons could be recognized:

'lvs --select lv_name=vg_name=abc' which would be equal to 'lvs --select lv_name=abc && vg_name=abc'

Explore more shortcuts that can be made to help creating more complex statements with less words (but keep the syntax simple!).

Comment 1 Peter Rajnoha 2014-06-24 12:07:22 UTC
(In reply to Peter Rajnoha from comment #0)
> If found usable for some situations, maybe also transitive comparisons could
> be recognized:
> 
> 'lvs --select lv_name=vg_name=abc' which would be equal to 'lvs --select
> lv_name=abc && vg_name=abc'

...or maybe 'lvs --select [lv_name,vg_name]=[abc...]' (this is probably easier to recognize for the parses because with the lv_name=vg_name=abc we have to take care whether the vg_name is the value to compare with or the field name (though the rule would be simple - count the number of operators chained and the value is typed after the last one). Explore what's better/more efficient and less error prone.

Comment 2 Peter Rajnoha 2024-08-12 10:34:45 UTC
No plan to implement this unless there's a demand from users.


Note You need to log in before you can comment on or make changes to this bug.