Skip to content

Main content

Random CSV Foreign Key Integrity Dataset Generator

Construct synthetic parent and child tables with an exact sampled orphan count, retaining reference truth, core match rate and orphan data-row indices.

Loading tool…

Description

Construct synthetic parent and child tables with an exact sampled orphan count, retaining reference truth, core match rate and orphan data-row indices.

CSV stores records as delimited text fields. Quoting can protect embedded delimiters and newlines, so a record need not equal one physical line. Cleaning field contents, interpreting their types, and preserving an exact import/export round trip are separate operations.

Construct synthetic parent and child tables with an exact sampled orphan count, retaining reference truth, core match rate and orphan data-row indices.

When to use this tool

Use this generator to create reproducible csv foreign key integrity dataset cases from the supplied model or bank. Inspect the returned evidence before using cases in a test or exercise.

How to use the tool and how it works

  1. Supply parentCount, childCount, orphanCount in the field shapes below. Set seed when you need an explicit replay.
  2. Run the tool and correct any input error. For generated controls, distinguish a successful fixture containing an invalid case from failure to generate the fixture.
  3. Read parents, children, orphanIndices, matchRate, parentCsv, childCsv. Use the conventions below. Keep answer-bearing fields separate when presenting an exercise.

Create parent keys and child records, sample exactly orphanCount child positions, and give those positions guaranteed absent keys. Delegate pair match rate and orphan-row detection, converting audit record indexes to zero-based child indexes.1

Delegated operations used for this result: foreign key column pair match rate; orphan rows parent key missing finder. Their calculation or parsing conventions apply to the corresponding result fields.2, 3

Input fieldMeaning and unitsAccepted input
parentCountParent CountRequired. Safe integer; minimum 1; maximum 16.
childCountChild CountRequired. Safe integer; minimum 1; maximum 32.
orphanCountOrphan CountRequired. Safe integer; minimum 0; maximum 32.
seedOptional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.Optional. Safe integer.
Output fieldInterpretationReturned shape
parentsParentsRequired. Array of Text; maximum UTF-16 length 64.; minimum items 0; maximum items 16.
childrenChildrenRequired. Array of Object; no unknown keys.; minimum items 0; maximum items 32.
children[].idLiteral identifier used independently of display labels.Required. Text; maximum UTF-16 length 64.
children[].parentKeyParent KeyRequired. Text; maximum UTF-16 length 64.
children[].orphanOrphanRequired. Boolean.
orphanIndicesOrphan IndicesRequired. Array of Safe integer; minimum 0; maximum 31.; minimum items 0; maximum items 32.
matchRateMatch RateRequired. Finite number; minimum 0; maximum 1.
parentCsvParent CsvRequired. Text; maximum UTF-16 length 100000.
childCsvChild CsvRequired. Text; maximum UTF-16 length 100000.
randomnessReplay source and normalized 32-bit seed, or null seed for an advancing context source.Required. Object; no unknown keys.
randomness.seedOptional safe-integer replay seed; normalization and precedence are explained below.Required. Safe integer. or Null.
randomness.sourceSourceRequired. Text; one of "context", "seed".

An explicit safe-integer seed takes precedence over injected context randomness and is normalized to an unsigned 32-bit integer. With no seed and no context source, replay uses the fixed tool.io default seed. A context source must return finite values from zero inclusive to one exclusive; its advancing state must be retained separately. randomness records the source and normalized seed, or null for context. These generators are not cryptographic random sources.

json
{
  "input": {
    "parentCount": 2,
    "childCount": 3,
    "orphanCount": 1,
    "seed": 42
  },
  "output": {
    "parents": [
      "P1",
      "P2"
    ],
    "children": [
      {
        "id": "C1",
        "parentKey": "P1",
        "orphan": false
      },
      {
        "id": "C2",
        "parentKey": "X2",
        "orphan": true
      },
      {
        "id": "C3",
        "parentKey": "P2",
        "orphan": false
      }
    ],
    "orphanIndices": [
      1
    ],
    "matchRate": 0.6666666666666666,
    "parentCsv": "parent\nP1\nP2",
    "childCsv": "child,parent\nC1,P1\nC2,X2\nC3,P2",
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • Known-parent children may repeat parent keys. Orphan flags are planted truth, not a database constraint repair. No database is created and match rate describes this finite constructed dataset.
  • A replay requires the same complete input and implementation. The stated sampling convention applies within its eligible space. A finite draw does not exhaust all possible outputs; repeats remain possible unless a distinct-selection rule is explicit.
  • The field tables state structural bounds; cross-field constraints and bounded search or output budgets also apply. Unknown keys are rejected where the object contract disallows them. Input errors are distinct from null fields and deliberate invalid controls in a successful output.

Alternative or Complementary methods

For a supplied example, inspect the returned construction or delegated check directly. To evaluate a consumer, also test cases chosen for its own boundaries; a generated finite corpus does not establish exhaustive coverage.

References

  1. Tool behavior and example: Random CSV Foreign Key Integrity Dataset Generator — tool.io

  2. Calculation or validation: csv/foreign-key-column-pair-match-rate — tool.io

  3. Calculation or validation: csv/orphan-rows-parent-key-missing-finder — tool.io

Similar or alternative tools