Support other data types than int and float

[ArnaudPalgen]

I'm starting to use tinyflux and I noticed in the documentation that the field values can only be int or float.

I find this very restrictive. What are the reasons for this restriction?

Do you think that adding bool or str is possible ?

[citrusvanilla]

You should use Tags for those types.

…

On Mon, Oct 14, 2024 at 5:11 PM ArnaudPalgen ***@***.***> wrote: I'm starting to use tinyflux and I noticed in the documentation that the field values can only be int or float. I find this very restrictive. What are the reasons for this restriction? Do you think that adding bool or str is possible ? — Reply to this email directly, view it on GitHub <#52>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB4EXVNGCTVEMORWZJ7FQ7TZ3ODFNAVCNFSM6AAAAABP4RCUPWVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZXGMYTKNJYG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ArnaudPalgen]

tags are not always the most appropriate field. Imagine a sensor that returns a true/false value, the value is true/false, and it's not a tag. This value does not need to be indexed.

Also, the documentation states that tinyflux follows the principles of InfluxDB, which accepts these data types as values (c.f. influxdb glossary)

If necessary, I can participate or work on a PR.
I remain open to the possible reasons why these types of data are not supported.

[citrusvanilla]

I'd be happy to review a PR for this work. But you'll have to code to the spec in the link:

Field values are not indexed - queries on field values scan all points that match the specified time range and, as a result, are not performant.