This release adds 1 notable feature for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
Summary
AI summaryAdds a Postgres facade so BI tools can connect to SLayer as if it were PostgreSQL.
Full changelog
SLayer 0.8.0: Add a Postgres facade for driving BI tools
Adds a Postgres facade, that is SLayer can now pretend to be Postgres so that BI tools can use it as a data source. If you point Metabase (or another BI tool that speaks the Postgres wire protocol) at SLayer, the queries it generates now translate and run correctly across schema introspection, breakouts, filters, and joins.
Dialect fixes
Several SQL-generation bugs are fixed for SQL Server (CTE inside a derived table, dotted ORDER BY references) and MySQL (identifier quoting when a query is wrapped in an outer select).
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
Track SLayer, a semantic layer maintained by your agent
Get notified when new releases ship.
Sign up freeAbout SLayer, a semantic layer maintained by your agent
All releases →Related context
Related tools
Earlier breaking changes
- v0.7.1 Changes `search()` response to a single flat `results` list capped by `max_results`, removing separate `memories`, `example_queries`, and `entities` buckets.
- v0.7.1 Changes `search()` to return a single flat `results` list, removing per‑bucket caps.
- v0.6.3 Datasource names now reject dots, slashes, nulls, empty/whitespace; existing names containing '.' will fail validation on upgrade.
- v0.6.0 recall_memories surface entirely removed with no deprecation shim.
- v0.5.1 Two-mode reference semantics enforced: SQL mode accepts arbitrary SQL; DSL mode strictly resolves identifiers.
Beta — feedback welcome: [email protected]