catalog::set_object_fields (crates/db/src/catalog.rs) validates field-by-field: one fields::field_definition_by_key query per key, plus one resolve_term/resolve_authority per term/authority key — an N+1 over the desired map.
Fine at single-object catalogue-entry scale. If/when bulk import lands (CSV/Excel → many objects), batch-fetch the relevant field definitions (and resolve references in bulk) once per import rather than per-field-per-object.
Source: Plan 5 (object flexible fields) final review — forward-looking, not relevant at current scale.
`catalog::set_object_fields` (`crates/db/src/catalog.rs`) validates field-by-field: one `fields::field_definition_by_key` query per key, plus one `resolve_term`/`resolve_authority` per term/authority key — an N+1 over the desired map.
Fine at single-object catalogue-entry scale. If/when **bulk import** lands (CSV/Excel → many objects), batch-fetch the relevant field definitions (and resolve references in bulk) once per import rather than per-field-per-object.
_Source: Plan 5 (object flexible fields) final review — forward-looking, not relevant at current scale._
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
catalog::set_object_fields(crates/db/src/catalog.rs) validates field-by-field: onefields::field_definition_by_keyquery per key, plus oneresolve_term/resolve_authorityper term/authority key — an N+1 over the desired map.Fine at single-object catalogue-entry scale. If/when bulk import lands (CSV/Excel → many objects), batch-fetch the relevant field definitions (and resolve references in bulk) once per import rather than per-field-per-object.
Source: Plan 5 (object flexible fields) final review — forward-looking, not relevant at current scale.