If I understood correctly, the intention of the extraction mechanism is to obtain the result of a query, which returns only one value, as a single variable instead of a list.
In it's current form, results of the form:
[(10,'2.6.57.13',5)]
are also processed through the "extraction" mechanism and incorrectly retrieve the value "10", dropping everything else.
This incorrect behavior is observed when, for example, entering into query mode and issuing the query: "SELECT * FROM file_statistics;"
If I understood correctly, the intention of the extraction mechanism is to obtain the result of a query, which returns only one value, as a single variable instead of a list.
In it's current form, results of the form:
[(10,'2.6.57.13',5)]
are also processed through the "extraction" mechanism and incorrectly retrieve the value "10", dropping everything else.
This incorrect behavior is observed when, for example, entering into query mode and issuing the query: "SELECT * FROM file_statistics;"
Yes, that's right, the extraction mechanism should avoid returning a list or tuple with only a single element.
I can reproduce the issue. I just checked your pull request, it looks like it solves it. I will merge it into the master branch now.
Yes, that's right, the extraction mechanism should avoid returning a list or tuple with only a single element.
I can reproduce the issue. I just checked your pull request, it looks like it solves it. I will merge it into the master branch now.
If I understood correctly, the intention of the extraction mechanism is to obtain the result of a query, which returns only one value, as a single variable instead of a list.
In it's current form, results of the form: [(10,'2.6.57.13',5)] are also processed through the "extraction" mechanism and incorrectly retrieve the value "10", dropping everything else.
This incorrect behavior is observed when, for example, entering into query mode and issuing the query: "SELECT * FROM file_statistics;"
Yes, that's right, the extraction mechanism should avoid returning a list or tuple with only a single element.
I can reproduce the issue. I just checked your pull request, it looks like it solves it. I will merge it into the master branch now.