Add support for Redis

[gunta]

It would be nice to have support for Redis.

[k1LoW]

I think Redis is a KVS.
I can't imagine documentation like RDMBS.
If you don't mind, could you describe using markdown what you want tbls to generate?

[gunta]

I was imagining using a process of automatic inference of schemas and data type based on introspecting the actual data.
This concept can be applied not only for Redis, but for other databases such as DynamoDB.

For the markdown I would expect inferred content similar to the current RDMBS support, but with just inferred Column and Data types. I wouldn't expect a graph, just the text.

These papers show some hints on how it would work:

• https://dspace.cuni.cz/bitstream/handle/20.500.11956/148825/120396893.pdf?sequence=1
• https://sbbd.org.br/2020/wp-content/uploads/sites/13/2020/09/207330_1-A-Process-for-Inference-of-Columnar-NoSQL-Database.pdf

[k1LoW]

It is a very attractive approach.

However, as long as it is inferential, is it not a 100% correct schema?
I am currently skeptical about documenting uncertain information since it is a document that engineers refer to for development purposes.

[gunta]

It's not exactly a "schema", but it would be more like a "reference" saying "hey, the current production/development data looks like this".

I can see this would help when new developers join a project in order to "see" how the data was structured before.
This would help understand, and make easy to plan or discuss new additions to the data.

So not much as "docs" but more as "reference".

[k1LoW]

It's not exactly a "schema", but it would be more like a "reference" saying "hey, the current production/development data looks like this".

It sounds very useful, but I think it is outside the scope of tbls' responsibilities.