athena introspection error

[jenstoll97]

Request for an option to set a default connection for Athena when creating new .sql or .dbcnb file from any location. 
 
When I click File > New File > DBCode Notebook, it opens up as "No connection, click to connect". When I do this, I can click on AWS (name of my connection) > AwsDataCatalog > but then it gets stuck on listing the schemas and never finds anything. 

If I create the .sql or .dbcnb file directly by right clicking on the connection within the DBCode extension tab, then it pops up with a connection already set. However, once I save the file, the connection will save on a .dbcnb file, but on a .sql file, it resets and goes back to "Select a connection" and I have the same error as above.

---

VSCode Version: 1.109.5
Extension Version: 1.28.4
OS: darwin
Arch: arm64
Database Version: -

[mikeburgh]

Let's try a couple things.

First, can you check if schemas load when you expand AwsDataCatalog in the sidebar tree (not the picker)? That'll help narrow down if it's the picker flow or introspection itself.

If it's also stuck there, try enabling progressive schema loading: edit the connection, scroll to Advanced > Introspection settings, and enable the progressive option. That changed how schemas are fetched and fixed similar issues for other Athena users.

If it's still not working after that, could you share the logs from Output > DBCode? That'll show if Athena is returning an error during introspection. Debug docs here: https://dbcode.io/docs/help-support/debug

On the .sql file losing its connection after save - that's a known limitation with untitled files. The connection is tied to the in-memory document, and once saved to disk it gets a new URI. If you create the .sql from the connection tree (right-click > New File), the connection metadata is stored differently and should persist. I can look into improving that. You can also use scratch files to create maps to connections and files.

[mikeburgh]

I actually stumbled across this issue and found the cause today. So it's fixed now in 1.28.11 which has been released.