-
Notifications
You must be signed in to change notification settings - Fork 40
Open
Description
Goal
Create the schemamapping table (or extend spquery with equivalent fields) to distinguish schema mapping queries from standard user queries.
Background
The schemamapping record wraps an spquery and adds metadata (MappingType, Name) necessary to segregate mappings from standard queries in the UI. Implementation approach (new table vs. extending spquery) is at the development team's discretion.
Schema (if new table)
| Field | Type | Notes |
|---|---|---|
| SchemaMappingID | Int (PK) | Auto-increment |
| QueryID | FK → spquery |
One-to-one, Required |
| MappingType | Enum (Core, Extension) |
Required |
| Name | VarChar | User-facing description |
| IsDefault | Boolean | Default false; system defaults are read-only |
Acceptance Criteria
- Table (or
spqueryextension) created in migration. -
MappingTypeenforced as enum with onlyCoreandExtensionvalues. - One-to-one relationship with
spqueryenforced. -
IsDefault = truerecords are read-only (cannot be edited or deleted via UI). - ORM model created and registered.
- Standard
spqueryrecords (non-mapping queries) are unaffected.
Reactions are currently unavailable