# `owner_search` migrations

These files build the **Owner Listing** schema, which lives in its own database
(`owner_search` on local MySQL) and is never part of the platform database.

They are **not** in `database/migrations/`, so `php artisan migrate` does not see
them. Run them explicitly, against the admin connection:

```bash
php artisan migrate --database=owner_listing_admin --path=database/migrations/owner_listing
```

`--database` puts both the tables **and** the `migrations` ledger inside
`owner_search`, so the schema is entirely self-contained — nothing about this
system appears in the lead database. Each migration also pins
`protected $connection = 'owner_listing_admin'`, so a forgotten flag cannot
create these tables in the platform database by accident.

The data itself is not seeded here. It is imported from the source archive:

```bash
php artisan owner:import /path/to/owner_search.db     # raw records
php artisan owner:build-index                          # profiles + name tokens
```

See [the module handbook](/docs/modules_handbook/manage/owner-listing/readMe.md).