Skip to content

Fix route/date analysis recipe and unsupported materialization guidance - #6

Open
josuecuguy1307 wants to merge 1 commit into
public-transport:mainfrom
josuecuguy1307:fix-route-date-recipe
Open

josuecuguy1307 wants to merge 1 commit into
public-transport:mainfrom
josuecuguy1307:fix-route-date-recipe

Conversation

@josuecuguy1307

Copy link
Copy Markdown

The route/date analysis recipe currently fails when copied: its WHERE clause contains a comma after the route_id predicate. It also recommends materialized-view, which lib/stats_by_route_date.js explicitly rejects. Remove the comma and document the supported view option.

Validation at revision 74c1e81:

  • Ran the original SQL against a controlled stats_by_route_date schema with DuckDB 1.5.6: Parser Error at the comma.
  • Ran the corrected SQL against matching-route/in-range, different-route and out-of-range rows: only the intended row returned.
  • Called the current createStatsByRouteAndDateView function with materialized-view: it raises “currently not supported”.
  • Whitespace check passed. Documentation only; no import/runtime behavior changed. This check is a recipe reproduction, not a full GTFS import benchmark.

Disclosure: submitted on behalf of ML DataMind's owner during GTFS consumer compatibility work. No promotional links or listings are added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant