---
title: "Comment by cevheri on \"Trino breaks the metadata assumptions a database IDE is built on\n\" | Hashnode"
description: "This is a brilliant breakdown of a classic \"leaky abstraction\" problem in database tooling. The shift from a rigid MetadataProvider interface to an EngineCapabi"
url: "https://hashnode.com/posts/trino-breaks-the-metadata-assumptions-a-database-ide-is-built-on/6a9c7206515a90af1170a69e/comment/6a9c740f70cfe52c2b6ad898"
---

[Discussion](https://hashnode.com/posts/trino-breaks-the-metadata-assumptions-a-database-ide-is-built-on/6a9c7206515a90af1170a69e)

Comment [Trino breaks the metadata assumptions a database IDE is built on](https://hashnode.com/posts/trino-breaks-the-metadata-assumptions-a-database-ide-is-built-on/6a9c7206515a90af1170a69e)

[cevheri](https://hashnode.com/@cevheri)

[Sep 5](https://hashnode.com/posts/trino-breaks-the-metadata-assumptions-a-database-ide-is-built-on/6a9c7206515a90af1170a69e/comment/6a9c740f70cfe52c2b6ad898)

This is a brilliant breakdown of a classic "leaky abstraction" problem in database tooling. The shift from a rigid MetadataProvider interface to an EngineCapabilities descriptor is exactly the right architectural pattern here. Assuming every backend behaves like a traditional single-node RDBMS is a trap many multi-engine client tools fall into.

I particularly love the nuance you added with writes: "connector". Deriving write permissions implicitly from primary keys is a silent bug waiting to happen, especially in federated query engines where a single Trino connection can span both a writable data lake and a read-only message broker.

Furthermore, hiding the UI entirely (e.g., removing the Indexes tab) instead of showing an empty list is a masterclass in "honest UX". It actively prevents users from drawing false conclusions.

The rule "declare capabilities, don't assume them" is a fantastic takeaway. Thanks for sharing this deep dive, it’s a great reference for anyone building tools that talk to diverse backends!
