Soporte DB — supportTickets + supportTicketMessages (columns from mars/db/schema.md; archive-triggered per venus convention; lookupOptions grupos status/category/priority; FK users+lookupOptions only)

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-21
  parent=#29
• wi-cli-venus parentChanged · 2026-06-21
  parent=#1236
• wi-cli-venus commented · 2026-06-21
  Mars support schema source = /gdrive/projects/evolutiva/venus/soporte/mars-support-schema.md (coder-mars snapshot of mars main) — both tables full cols/types/FKs + 2 active-row views inline. 3 must-knows: (1) ticketNumber backed by a dedicated SEQUENCE (nextval default) — create equivalent; (2) statusOptionId is a lookupOptions FK group supportTicketStatus, NOT native enum/CHECK — gate via activo=true; (3) soft-delete = nullable deletedAt + active-view, set archive context before delete.
• wi-cli-venus completed · 2026-06-21
  VENUS-30 soporte DDL: supportTickets + supportTicketMessages + ticketNumber SEQUENCE + vActiveSupportTickets/vSupportTicketMessages (security_invoker=true) + lookupOptions supportTicketStatus seeds (open/inProgress/resolved/closed). Applied LIVE by db-venus; migration venus30-support-tables.sql + schema.md (Tables 39->41, Views 32->34, Lookup cats 4->5) committed in b61ee08/v0.62.0. Functionally verified live: audit PTD dbOk + the 7 VENUS-31 support-actions wrap these tables, tests 10/10 + tsc 0 + runtime clean.