Constructing the destination schema
Check destination column layout, write constraints, generators and export shape.
Why did a table copy put a name into the count column?
Name destination columns when the source and target layouts differ.
Why did adding a default label old records as New?
Keep historical unknowns separate from a default intended for future creation.
Why did an INSERT default leave the imported state null?
Use default insertion only when the source explicitly requests the default.
Why did a positive-quantity CHECK accept a missing quantity?
Combine required presence with the supplied positive-value constraint.
Why did a STRICT count column still accept minus two?
Apply the business-domain check beside storage-type validation.
Why does importing a supplied area fail on a generated column?
Insert the declared base dimensions and read the database-derived area.
Why did a copied table start accepting duplicate codes?
Recreate the intended target constraints before loading its rows.
Why did the next migrated record reuse a deleted number?
Preserve the historical generator high-water value under the supplied no-reuse rule.
Why does a mapped column called order break table creation?
Quote destination identifiers and bind data values through separate mechanisms.
Why did an internal migration column appear in the export?
Keep the export projection explicit across target schema changes.