More powerful Object Query Language Needed

Product Feedback
1

The current accepted Object-Query-Language (OQL) in AIP Studio is lacking in some expected capabilities.

For example, a query can only reference a single object. Then you can use the result to query a related object. This often then requires multiple steps of interaction with the LLM for a single activity. Its not impossible, its just slow. And this degrades the user experience.

One cannot use SELECT, ORDER BY, or LIMIT statements, which the LLM keeps trying to do (unless you include additional prompt instructions to warn the LLM).

I am constantly correcting the OQL errors with improved prompting instructions. This takes away time and focus from the core aspects of my work.

Overall, my sense is that OQL is still in an early version and needs to be upgraded to get to the level expected (by the LLMs at least).

2

Thanks for flagging this! The existing domain-specific language we have for the current object query tool is lacking.

We’ve been working hard the past few months on a new object query tool backed by SQL. This new tool will be faster and support more complex queries in one iteration. We expect to release this in a couple weeks and would appreciate any feedback you have.

3

Perfect, a full SQL approach will be easier for the LLMs to get right as well. Looking forward to it.