Direct schema update via API #297
Replies: 3 comments 6 replies
-
|
Fully agree, we need this! I'll sketch this soon. |
Beta Was this translation helpful? Give feedback.
-
|
Small update here: I added support for catalogs and the dynamic registration of schemas. A first example of the JS api can be found here: https://github.com/ankoh/sqlynx/blob/b8e51e153b11a326a4de32df435b6b48fbb8cd70/packages/sqlynx-wasm/test/catalog.test.ts#L21-L71 Maintaining these descriptor pools is cheap and resolving names is fast against both, a large number of pools as well as pools with many schemas and tables. |
Beta Was this translation helpful? Give feedback.
-
|
Hello André, I wanted to thank you for making those changes so quickly. They seem to really solve the problem I faced, just as I hoped. I apologize for the delayed response. I've just started testing the changes. I'll provide feedback once I've completed the integration and testing. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
First of all, thank you for such a powerful tool!
I am excited to use sqlynx to provide autocomplete features within our browser-based code editor.
However, I've encountered some limitations, particularly when it comes to efficiently handling databases with a large number of tables. Currently, the tool requires an external script containing SQL instructions (e.g., CREATE TABLE) for accurate hints.
The issue arises in terms of performance, especially with databases containing thousands of tables. Parsing this script for schema information impacts performance by freezing the page for several seconds.
It would be nice to have additional API methods that allow direct updates to the completion index with new identifiers. Ideally, these changes could look like:
With packing data into corresponding flatbuffers structure.
Here's a bit of context regarding our usage scenarios:
analyzedScript.tableReferencesandanalyzedScript.columnReferences, searching for matches within our internal storage and updating the schema.Implementing these changes would significantly enhance performance, especially in scenarios with massive database schemas.
Thank you for considering these changes!
Beta Was this translation helpful? Give feedback.
All reactions