okhp3-notion-query

Topics in the source

• okhp3-notion-query
• Scope
• The mandatory prerequisite
• Three modes
• Rows mode specifics
• SQL mode caveats - read before trusting output
• View mode specifics
• Output contract

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Reads rows from a known Notion data source. Always load okhp3-notion-core first, and okhp3-notion-identity-resolution if the data source is not yet a confirmed ID. | In scope | Out of scope | |---|---| | SQL mode, rows mode, saved-view mode against a resolved data source | Finding content by keyword (okhp3-notion-search-strategy). Page body content (okhp3-notion-page-read). Any write (okhp3-notion-row-write) | Every query targets a data source, never a bare databaseid. If the caller has only a database reference, resolve it first: fetch the database, read datasources[], and use the correct datasourceid. This is okhp3-notion-core's Step 4 rule, restated here because it is the most common failure point in query work specifically. | Mode | Use when | Cost model | |---|---|---| | View mode | The user wants exactly what a saved view already shows | Free on every plan, no tool-specific quota | | Rows mode | Simple filter/sort against one data source, no custom aggregation needed | Metered on non-Business/Enterprise plans, shares an allowance with single-data-source SQL | | SQL mode | Complex joins, aggregation, or multi-data-source q

This is an excerpt. Refer to the complete source and its current requirements.