Sorry about that! I just tested with the same DBeaver version and was unable to reproduce the bug. If you email support@splitgraph.com with your username, we can check the logs and figure out the problem for you.

In general, some clients will have issues with introspection queries (which they use to show the list of available schemas). And even when introspection works, we can't show you all 40k datasets or it might break your client. So we just show "featured" datasets, and for a more exhaustive list you can go to the website to find a dataset.

But, you can still query any dataset on Splitgraph regardless of what shows in your client's schema list. You can go to https://www.splitgraph.com/explore to find datasets, and from each dataset's repo page, you can click "tables" or "query SQL" to get a sample SQL query to run.

I think we fixed this now, was a bug in how we did our client introspection query rewrites (wasn't actually DBeaver-specific).

Could you try again when you have the chance?