Generate selected tables and columns in structured batches #8

Closed
opened 2026-08-28 13:34:16 +00:00 by mptyl · 0 comments
Owner

Parent

#4

What to build

Extend the first generation path to selected Catalog Tables and multiple selected Catalog Columns, processing sequential structured requests of at most ten targets and validating every target mapping before applying results.

Acceptance criteria

  • Existing table and column checkbox selections expose the relevant generation actions.
  • Multiple targets are divided into requests of at most ten and model requests execute one at a time.
  • Responses map generated or non-generatable outcomes unambiguously to requested targets.
  • Duplicate, unknown, missing, or malformed target mappings make the request fail and apply none of that ambiguous response.
  • Generated prose is requested in the workspace language.
  • A valid non-generatable outcome writes the application's standard localized value, such as Non generabile for an Italian workspace.
  • Technical failures never write the non-generatable value.
  • Table prompts use current structural facts and available curated or generated column descriptions.
  • Progress counters and events remain correct for multiple batches and both target kinds.
  • Fastify/PostgreSQL and Database Management tests cover tables, columns, batch boundaries, ordering, localization, and malformed responses.

Blocked by

  • #7 — Generate one selected Catalog Column asynchronously
## Parent https://git.tylconsulting.it/mptyl/ThothII/issues/4 ## What to build Extend the first generation path to selected Catalog Tables and multiple selected Catalog Columns, processing sequential structured requests of at most ten targets and validating every target mapping before applying results. ## Acceptance criteria - [ ] Existing table and column checkbox selections expose the relevant generation actions. - [ ] Multiple targets are divided into requests of at most ten and model requests execute one at a time. - [ ] Responses map generated or non-generatable outcomes unambiguously to requested targets. - [ ] Duplicate, unknown, missing, or malformed target mappings make the request fail and apply none of that ambiguous response. - [ ] Generated prose is requested in the workspace language. - [ ] A valid non-generatable outcome writes the application's standard localized value, such as Non generabile for an Italian workspace. - [ ] Technical failures never write the non-generatable value. - [ ] Table prompts use current structural facts and available curated or generated column descriptions. - [ ] Progress counters and events remain correct for multiple batches and both target kinds. - [ ] Fastify/PostgreSQL and Database Management tests cover tables, columns, batch boundaries, ordering, localization, and malformed responses. ## Blocked by - #7 — Generate one selected Catalog Column asynchronously
mptyl added the enhancementready-for-agent labels 2026-08-28 13:34:16 +00:00
mptyl added a new dependency 2026-08-28 13:34:57 +00:00
mptyl added a new dependency 2026-08-28 13:35:00 +00:00
mptyl added a new dependency 2026-08-28 13:35:03 +00:00
mptyl closed this issue 2026-08-28 15:28:59 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: mptyl/ThothII#8