Add CLAUDE.md: document why extension_drop needs schema-independence testing - #35
Conversation
…testing extension_drop's control file omits schema=, making it genuinely install-schema-flexible, but the current test suite only proves this via one dedicated file (test/sql/schema.sql) rather than across the whole suite. Record the rationale and the correct pattern (a TEST_SCHEMA switch mirroring TEST_LOAD_SOURCE, per Postgres-Extensions/pg_count_nulls#28) so it isn't rediscovered from scratch, or missed, next time.
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Claude finished @jnasbyupgrade's task in 2m 55s —— View job Claude finished reviewing this PRTodo list:
ReviewThis is a doc-only addition (
One accuracy nit worth a look before/after merge:
Neither I wasn't able to fetch Everything else — the reasoning about search_path-absence and mixed-case/quoting being independently necessary, and marking this as documentation-only with implementation as tracked follow-up — is sound and consistent with the current code. No blocking issues; the one nit above is optional polish. |
Summary
extension_drop's control file has noschema=line, making it genuinely install-schema-flexible (confirmed against actual PostgreSQL semantics:schema=, notrelocatable=, is what pins install-time schema choice).test/sql/schema.sql), not across the whole suite.TEST_SCHEMAswitch mirroringTEST_LOAD_SOURCE's existing GUC-propagation mechanism, perPostgres-Extensions/pg_count_nullsCI: fix claude-code-review by removing the fork-checkout step entirely #28 (a working reference implementation already in the org).This is documentation only — no test/build changes. Implementing the actual
TEST_SCHEMAdimension is tracked as follow-up work.Test plan