[bug]:When the query result is empty, the client will report a null pointer exception.

[joyant]

[bug]:When the query result is empty, the client will report a null pointer exception.

[joyant]

I can fix this bug, but before fixing it, I hope we can reach a consensus.

The root cause of this bug is caused by the m.Values.([]interface{}) assertion in the github.com/lindb/common/models/metadata.go file, but I prefer to fix it in the ExecuteAsResult function of the github.com/lindb/internal/client/execute.go file. The solution is to assert the formatter and determine whether Values is nil, if it is empty, a friendly prompt will be output.

At the same time, I also want to add the recover method at the top of the ExecuteAsResult method to prevent lindcli from crashing.

In addition, can I change the color of the input sql text?

[stone1100]

The root cause is getting zero results from the server when no data is found, this bug can be fixed according to your solution. Can recover at the top of cli execute method then return error message.

Or return an empty result not nil if there is no data, it can make api/cli to return empty.
https://github.com/lindb/lindb/blob/main/query/search.go#L163-L216

[stone1100]

Currently some common query cases are supported in LinDB cli.