Conversation
modified the response of the getSchemaTree endpoint to include constraints and indexes for improved the auto-completion provided in the sql query console of the Polypheny-UI
|
Hi, @hennlo I need some help,plz |
|
Hi @alyaa999 What do you mean by 'in a sperate endpoint'? |
@hennlo I mean that the getSchemaTree method retrieves objects situated under schemas, whereas adapters and the query interface are not part of the schema. Therefore, we should create a new method to specifically return adapters and the query interface, and then add it to the suggestion list in the editor component (Polypheny-UI) |
|
@alyaa999 Ah okay I get the question now, thanks for clarifying. Yes indeed a separate method(s) would be desirable since adapters and inetrfaces are not part of any schema 👍 |
add methid to gell all query interface names
|
I have a question related to the "getSchemaTree" method. This method accepts a parameter called "depth," and the user interface (UI) sends a request with a depth of 3, indicating schemas, tables, and columns. My question is whether I should adjust this depth to 5 or 4 to express constrains and indexes |
Summary
Add missing identifiers to the list of suggested names in the auto-completion provided in the SQL query console of the Polypheny-UI.
Fixes #43
ToDo