Repository navigation
v0.1.2
Fixes
-
Prefer WHERE clause value for query/path param columns — When a column is used as a query or path parameter, the FDW now injects the WHERE clause value directly into result rows instead of using the API response value. This fixes a case mismatch issue where APIs accept one casing (e.g.
?status=actual) but return another (e.g."Actual"), which caused PostgreSQL's post-filter to drop all rows. (Fixes #2) -
Inject query param values back into result rows — Query parameters extracted from WHERE clauses are now stored and injected back into rows when the API response doesn't contain the field. Previously, query-param-only columns (like
region_type) would be null, causing PostgreSQL's post-filter to drop all rows. (Fixes #1)
Full Changelog: v0.1.0...v0.1.2