The Ancestry_Kit table holds the A* sign-in record used by the client to reach an account’s test profiles. It is a small, internal bookkeeping table — one row per stored login — not a store of DNA matches.
DNA_Kits table.| Column | Type | Source | Description |
|---|---|---|---|
| Id | int (PK) | Auto | Auto-incrementing primary key |
| kitnumber | string | App | Kit number for the login. Not set by the current login flow. |
| username | string | App | The A* account username used to sign in |
| password | string | App | Internal credential storage for the login. The current login flow writes an empty value here. |
| created_date | string | App | Date the row was created (MM/dd/yyyy) |
| sync | string | App | Sync status flag (set to “0” on insert) |
| loginUsername | string | App | The DNAGedcom username that owns this record |
A row is added after a successful A* sign-in. Inserts are de-duplicated on the username/password pair, so signing in again with the same credentials does not create a duplicate row. The loginUsername and sync fields are stamped by the client at insert time.