Bulk Import -- Identifiers & Operations
Bulk Import supports two independent identifier types for row resolution.
Identifier Types
idInternal immutable primary key generated by Minyu._idExternal mutable reference key supplied by the importing system.
Both identifiers exist on all tables by default.
Resolution Rules
- If
idis present, it is always used as the primary lookup key. - If only
_idis present, Minyu resolves the row using_id. - If both are present,
idtakes precedence and_idis updated if provided. - If neither is present:
INSERTis allowedUPDATEandDELETEare rejected and will raise errors
Relationship Identifier Rules
For relations represented as foreign keys in the importing table:
<relation>→ contains the target row'sidvalue_<relation>→ contains the target row's_idvalue
For many-to-many link files:
source/_sourcetarget/_target
At least one identifier variant must be supplied per reference.
Operation Semantics
The _operation column defines the mutation applied to each row:
INSERT→ creates a new rowUPDATE→ modifies an existing rowDELETE→ removes an existing row
Constraints
UPDATErequires resolvableidor_idDELETErequires resolvableidor_id- Many-to-many files only allow
INSERTandDELETE