[godshatter]

The more detailed you have to get explaining things, the less I would want to use it. If I can say something like "get the employee's pay-related data" and not have to delineate exactly what fields to get and what to call them, that would be useful. If I could say "make sure they are not also a student" (I work for a university) and have it figure that out, that would also be useful. If I have to tell it what joins to make I'd rather just type it in in sql or whatever it's underlying language is. Typing is much more casual of an activity for me than speaking is, and I can type for hours at a time and I can't talk for that long without my throat running dry. If I can say in a few words what I want and save a lot of typing, then that's great. If I end up saying as much a I would type anyway, then I'd rather just type it.

I think this is definitely something that should be looked at, but it's not a product I'm really interested in unless it wows me with it's intelligence. It has to start somewhere, though. I'm probably an outlier in the sense that I think a lot of people would rather talk to their computer than type on a keyboard. I'm just not one of them. I also don't want to work in cubicle hell with everyone speaking to their computer 24/7.

[brochington]

Ah, sorry, I should clarify that when I say "talk", I didn't mean it in the literal sense. I've only worked on text as a source, though Speech-to-text shouldn't be too hard to integrate if it was needed.

I like your insight about using... let's call them "key phrases"...to help guide the query. Perhaps having a way to map a key phrase with a specific query, maybe one that is parameterized, would be useful. thank you.