Roadmap and feature proposals ​

Use the current public documentation to decide whether an application can depend on a capability today. A requested feature, compatibility experiment or proposed integration is not a release commitment. This page does not assign delivery dates to proposed work.

Describe the application need ​

A useful proposal includes the operation a user needs, a small input and the expected observable result. State the interface involved and explain what the application does today. Link to the relevant SQL reference, format or connection guide.

Separate a missing capability from a reproducible failure of documented behavior. For a failure, provide a regression case with the tested executable and actual output. For a new capability, describe the result and error behavior an integration would need to rely on.

Assess readiness through evidence ​

Before an application adopts a change, verify that its target executable implements the behavior, its documentation describes the boundary and an integration test covers the application's case. Record limitations that still affect the caller. Avoid inferring availability from a page title or an example for a different database.

See integration development for turning a concrete application requirement into a tested adapter contract.