Isn't it a problem with many-to-many relationships in relational algebra? You have to have this artificial table to relate things in many-to-many way. How would you display it in a better way?

The tables should be better ordered. "speakers" is obviously the primary table here and should be top left. The "session_speakers" should be between it and the table it maps "sessions." Then "reviews" and "events" on the bottom. There's an obvious "top end" and "bottom end" of this structure that this graph completely gets wrong.

You could argue that "events" are primary in which case just switch the order of that and "speakers."

I'd color the table headers differently and different from each other and have the arrows leaving that box match the color of the box it's leaving. Also drop "public:". It's expected and default so it does not need to be displayed here.

Drop the key icon and just make the key fields in bold or with a different style.

Don't make me hunt around to match information and don't be afraid to use differential styling.

That's great feedback! Thank you! I wonder if we can auto-layout in the way you describe. Should be doable. We will look into it.

PM on the project here - The results from the query are generally not used by the LLM. In agent mode though, during query planning, the agent may retrieve sample of the data to improve precision of the queries. For example, getting distinct values from dimensional table to resolve filter condition from natural language statement.

Thanks. I worry about these kind of tools connecting to production databases.. Especially considering how easy it is to switch out LLM endpoints, where that data is going, how it is retained, the context etc becomes a bit of a privacy nightmare..

Absolutely valid concern. Our extension connects to LLMs through Github Copilot. Github Copilot is Microsoft product and offers variety of enterprise plans, which enables your IT to approve what can be used for what kind of data. This gives you a clear path towards compliance with your enterprise requirements.

Makes sense. Appreciate the responses. Honestly though, as a person outside the US, I'm removing my dependence on US company IT tools and infrastructure, GitHub, VSCode, AWS etc, enterprise or otherwise.. Congrats on the project though.

PM on the project here - All clouds and on-prem/local/docker work great! We test those, so if you have issues, please report in the repo we'll fix them.

PM on the project here - Yes! It works on any Postgres, on-prem or cloud

Hi maxlux, is it possible to configure a connection over SSH?

Not directly in the extension connection object, but it's in on the roadmap. In the meantime, you can create ssh tunnel using vscode remotes and then just connect through it.

Would you be interested if this extension supported all of the psql commands directly in the vscode editor?

I am PM from the project - short answer is yes - you can connect to any Postgres endpoint. There are some Azure specific features, like EntraID supported by the extension that don't exist in other cloud providers.

Thank you, this is great

Thanks so cool

If you have any questions, please let us know. maxluk [MSFT]