|
|
|
|
|
by coolgeek
1661 days ago
|
|
Explainability is always helpful :) Simple SQL statements are pretty well self-documenting. Where things get hard to explain is in: * complicated JOINs
* queries that select from views, derived tables, CTEs, etc
* poorly named objects (tables, columns)
* dynamically constructed queries (e.g. really ugly WHERE clauses generated in a web app)
* queries generated by ORMs
Those are just off the top of my head. I'm sure there are several other sources of pain.The other big question is - why do you want to devote your time and effort to it? I don't want to discourage you. But I don't see any real path to a marketable product here, particularly not as a standalone product. |
|
> The other big question is - why do you want to devote your time and effort to it? I don't want to discourage you. But I don't see any real path to a marketable product here, particularly not as a standalone product.
This is a really good question, that's why I am collecting feedback on the idea :)
I've been thinking about building data catalog product, but it seems there are so many of them out where. So I thought I shoud somehow make if diffirent (and better), that's why I came up with SQL-To-Text idea.
Probably, you are right, I also don't see it as a standalone product. Perhaps, it can be a feature in data catalog / lineage product.