A more intelligent & useful history file & way to query it

[kilasuit]

It would be great to have a much more intelligent & complex history file than the current simple implementation that we currently have, although to achieve this I expect that it would likely be much more computationally expensive than the current implementation.

Ideally I would like to see this be more structured & complex and able to be queried in a way that allows for much better analytics of common command use that enables inspection on the count of use being aliased or using the full command name, common parameter combinations as well as a count of the use of each parameter & arguments to that parameter.

Some loose goals

• Local Sqlite file - Default option
• Remote sqllite or other db format (for cross machine history reasons) - Configurable option
• Configuration options - including continue to use current file for those that want it
• Initial base DB Schema
• User Extensibility of DB Schema
• Additional Querying cmdlets

[lzybkr]

Cross session sharing makes this somewhat hard to implement without a proper database.

I see sqlite might be a reasonable option.

[daxian-dbw]

The suggestion to use Frecency algorithm for history prediction (#1808) and also possibly a local ML model to provide predictions from the history patterns would also require a more powerful storage for history. So yes, we can look into replacing the history file with sqlite.

[kilasuit]

@daxian-dbw This still would be a big win for PSReadline going forward and it would be great if you and I could find some time together to make it happen