pattern option for t.list and t.remove

[veroandreo]

Would that be possible to have a "pattern" option both in t.list and t.remove (as we have in g.list and g.remove) to make it easier to search and remove stds according to a pattern in their name??

[lucadelu]

Soeren (and all) I looked into code of t.list and I discovered two possible way to implement this:

• simpler add into get_dataset_list function a LIKE operetor passing the pattern string
• more complex using the python fnmatch module to fetch the right databases, but in this case we should get always the name of dataset in the query and later check if it is a required column otherwise not print/write the field

What do you suggest? (also other ways are welcome)

Solving the list problem also the remove one should be simpler to implement.

[martinl]

Milestone renamed

[lucadelu]

Could someone answer to my question?

so I could work on this ticket...

[veroandreo]

G7:t.unregister would also benefit from a "pattern" option :)

[neteler]

Replying to lucadelu:

Soeren (and all) I looked into code of t.list and I discovered two possible way to implement this:

• simpler add into get_dataset_list function a LIKE operetor passing the pattern string

Would there be the problem that the LIKE operator behaviour then depends on the DB backend?

• more complex using the python fnmatch module to fetch the right databases, but in this case we should get always the name of dataset in the query and later check if it is a required column otherwise not print/write the field

What do you suggest? (also other ways are welcome)

Solving the list problem also the remove one should be simpler to implement.

Overall, it would be good to achieve a similar usability as for g.list/g.remove if all possible.

[neteler]

Ticket retargeted after milestone closed

[martinl]

All enhancement tickets should be assigned to 7.6 milestone.

[martinl]

Ticket retargeted after milestone closed

[martinl]

Ticket retargeted after milestone closed