@byline/db-mysql 4.8.0

package/LICENSE

@@ -0,0 +1,373 @@
+Mozilla Public License Version 2.0
+==================================
+
+1. Definitions
+--------------
+
+1.1. "Contributor"
+    means each individual or legal entity that creates, contributes to
+    the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+    means the combination of the Contributions of others (if any) used
+    by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+    means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+    means Source Code Form to which the initial Contributor has attached
+    the notice in Exhibit A, the Executable Form of such Source Code
+    Form, and Modifications of such Source Code Form, in each case
+    including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+    means
+
+    (a) that the initial Contributor has attached the notice described
+        in Exhibit B to the Covered Software; or
+
+    (b) that the Covered Software was made available under the terms of
+        version 1.1 or earlier of the License, but not also under the
+        terms of a Secondary License.
+
+1.6. "Executable Form"
+    means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+    means a work that combines Covered Software with other material, in
+    a separate file or files, that is not Covered Software.
+
+1.8. "License"
+    means this document.
+
+1.9. "Licensable"
+    means having the right to grant, to the maximum extent possible,
+    whether at the time of the initial grant or subsequently, any and
+    all of the rights conveyed by this License.
+
+1.10. "Modifications"
+    means any of the following:
+
+    (a) any file in Source Code Form that results from an addition to,
+        deletion from, or modification of the contents of Covered
+        Software; or
+
+    (b) any new file in Source Code Form that contains any Covered
+        Software.
+
+1.11. "Patent Claims" of a Contributor
+    means any patent claim(s), including without limitation, method,
+    process, and apparatus claims, in any patent Licensable by such
+    Contributor that would be infringed, but for the grant of the
+    License, by the making, using, selling, offering for sale, having
+    made, import, or transfer of either its Contributions or its
+    Contributor Version.
+
+1.12. "Secondary License"
+    means either the GNU General Public License, Version 2.0, the GNU
+    Lesser General Public License, Version 2.1, the GNU Affero General
+    Public License, Version 3.0, or any later versions of those
+    licenses.
+
+1.13. "Source Code Form"
+    means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+    means an individual or a legal entity exercising rights under this
+    License. For legal entities, "You" includes any entity that
+    controls, is controlled by, or is under common control with You. For
+    purposes of this definition, "control" means (a) the power, direct
+    or indirect, to cause the direction or management of such entity,
+    whether by contract or otherwise, or (b) ownership of more than
+    fifty percent (50%) of the outstanding shares or beneficial
+    ownership of such entity.
+
+2. License Grants and Conditions
+--------------------------------
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+    Licensable by such Contributor to use, reproduce, make available,
+    modify, display, perform, distribute, and otherwise exploit its
+    Contributions, either on an unmodified basis, with Modifications, or
+    as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+    for sale, have made, import, and otherwise transfer either its
+    Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+    or
+
+(b) for infringements caused by: (i) Your and any other third party's
+    modifications of Covered Software, or (ii) the combination of its
+    Contributions with other software (except as part of its Contributor
+    Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+    its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+-------------------
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+    Form, as described in Section 3.1, and You must inform recipients of
+    the Executable Form how they can obtain a copy of such Source Code
+    Form by reasonable means in a timely manner, at a charge no more
+    than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+    License, or sublicense it under different terms, provided that the
+    license for the Executable Form does not attempt to limit or alter
+    the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+---------------------------------------------------
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+--------------
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+************************************************************************
+*                                                                      *
+*  6. Disclaimer of Warranty                                           *
+*  -------------------------                                           *
+*                                                                      *
+*  Covered Software is provided under this License on an "as is"       *
+*  basis, without warranty of any kind, either expressed, implied, or  *
+*  statutory, including, without limitation, warranties that the       *
+*  Covered Software is free of defects, merchantable, fit for a        *
+*  particular purpose or non-infringing. The entire risk as to the     *
+*  quality and performance of the Covered Software is with You.        *
+*  Should any Covered Software prove defective in any respect, You     *
+*  (not any Contributor) assume the cost of any necessary servicing,   *
+*  repair, or correction. This disclaimer of warranty constitutes an   *
+*  essential part of this License. No use of any Covered Software is   *
+*  authorized under this License except under this disclaimer.         *
+*                                                                      *
+************************************************************************
+
+************************************************************************
+*                                                                      *
+*  7. Limitation of Liability                                          *
+*  --------------------------                                          *
+*                                                                      *
+*  Under no circumstances and under no legal theory, whether tort      *
+*  (including negligence), contract, or otherwise, shall any           *
+*  Contributor, or anyone who distributes Covered Software as          *
+*  permitted above, be liable to You for any direct, indirect,         *
+*  special, incidental, or consequential damages of any character      *
+*  including, without limitation, damages for lost profits, loss of    *
+*  goodwill, work stoppage, computer failure or malfunction, or any    *
+*  and all other commercial damages or losses, even if such party      *
+*  shall have been informed of the possibility of such damages. This   *
+*  limitation of liability shall not apply to liability for death or   *
+*  personal injury resulting from such party's negligence to the       *
+*  extent applicable law prohibits such limitation. Some               *
+*  jurisdictions do not allow the exclusion or limitation of           *
+*  incidental or consequential damages, so this exclusion and          *
+*  limitation may not apply to You.                                    *
+*                                                                      *
+************************************************************************
+
+8. Litigation
+-------------
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+----------------
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+---------------------------
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+Exhibit A - Source Code Form License Notice
+-------------------------------------------
+
+  This Source Code is subject to the terms of the Mozilla Public
+  License, v. 2.0. If a copy of the MPL was not distributed with this
+  file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+Exhibit B - "Incompatible With Secondary Licenses" Notice
+---------------------------------------------------------
+
+  This Source Code is "Incompatible With Secondary Licenses", as
+  defined by the Mozilla Public License, v. 2.0.

package/README.md

@@ -0,0 +1,283 @@
+# @byline/db-mysql
+
+> **Status: preliminary.** This adapter is published so it can be evaluated and
+> exercised, not because MySQL is a fully supported Byline backend yet. The
+> storage layer is complete and proven — it passes the entire shared
+> `@byline/db-conformance` behavioural suite, the same suite `@byline/db-postgres`
+> passes, with identical results. What is missing is the surrounding ecosystem:
+>
+> - **No search provider.** `@byline/search-postgres` has no MySQL counterpart, and
+>   this is not merely a missing feature — `initBylineCore()` **throws at boot** if
+>   any collection declares `search` and no provider is registered. See
+>   [Search on MySQL](#search-on-mysql) below for the one-step workaround you will
+>   need. Tracked in
+>   [#52](https://github.com/Byline-CMS/bylinecms.dev/issues/52).
+> - **No CLI support.** `byline init` scaffolds a Postgres installation; wiring
+>   MySQL is a manual edit to your `server.config.ts`.
+> - **Narrower CI coverage than Postgres.** Continuous integration pins MySQL 8.0
+>   — the engine floor — so nothing yet exercises 9.x automatically, and no leg
+>   runs under a non-UTC timezone. Tracked in
+>   [#55](https://github.com/Byline-CMS/bylinecms.dev/issues/55).
+>
+> Treat it as suitable for evaluation, prototypes, and installations that do not
+> need search. The criteria for general availability are tracked in
+> [#58](https://github.com/Byline-CMS/bylinecms.dev/issues/58).
+
+MySQL adapter for Byline CMS — Drizzle schema, migrations, and the storage /
+queries / commands implementation behind `IDbAdapter`. It is Byline's second
+database adapter, alongside `@byline/db-postgres`. The subpath
+`@byline/db-mysql/admin` ships the MySQL-backed admin-store repositories that
+plug into `@byline/admin`, the same way `@byline/db-postgres/admin` does.
+
+Both adapters implement the same `IDbAdapter` contract and pass the same
+shared `@byline/db-conformance` behavioural suite, so document storage,
+versioning, patches, workflow, populate, and admin auth behave identically
+regardless of which database backs an installation. See
+[Core Document Storage](https://github.com/Byline-CMS/bylinecms.dev/blob/develop/docs/03-architecture/01-document-storage.md)
+for the storage model both adapters implement.
+
+This package is part of [Byline CMS](https://github.com/Byline-CMS/bylinecms.dev)
+— a developer-friendly, open-source headless CMS with versioning, editorial
+workflow, and content translation as first-class concerns.
+
+## Install
+
+```sh
+pnpm add @byline/db-mysql
+```
+
+`mysql2` is a direct dependency, so no separate driver install is required.
+
+## Usage
+
+`mysqlAdapter()` takes a connection string, your `CollectionDefinition[]`, and
+the installation's default content locale, and returns an `IDbAdapter` (plus
+the underlying `drizzle` handle and `pool`, exposed for housekeeping and
+migration tooling):
+
+```ts
+import { initBylineCore } from '@byline/core'
+import { mysqlAdapter } from '@byline/db-mysql'
+import { createAdminStore } from '@byline/db-mysql/admin'
+
+import { collections } from './byline/collections/index.js'
+import { i18n } from './byline/i18n.js'
+import { routes } from './byline/routes.js'
+
+const db = mysqlAdapter({
+  connectionString: process.env.BYLINE_DB_MYSQL_CONNECTION_STRING!,
+  collections,
+  defaultContentLocale: i18n.content.defaultLocale,
+  connectionLimit: 20, // optional — mysql2 pool size, defaults to 20
+})
+
+const core = await initBylineCore({
+  serverURL: process.env.VITE_SERVER_URL!,
+  i18n,
+  routes,
+  collections,
+  db,
+  adminStore: createAdminStore(db.drizzle),
+  // storage, search, hooks, … — see @byline/core's ServerConfig type
+})
+```
+
+This mirrors how `apps/webapp/byline/server.config.ts` wires `@byline/db-postgres` today —
+swap `pgAdapter` / `@byline/db-postgres/admin` for `mysqlAdapter` /
+`@byline/db-mysql/admin` and the rest of an existing Byline server config is unchanged,
+because both adapters implement the same `IDbAdapter` and `AdminStore` contracts.
+
+`connectionString` is the **only** connection input `mysqlAdapter` takes, and
+it must be a `mysql://` URL — mysql2 parses connection URLs natively (`uri`
+is a first-class `createPool` option), so there is no separate host / port /
+user / password / database set of fields to keep in sync with it. An earlier
+version of this package's `.env.example` implied the URL existed only to
+serve the `db_init.sh` / `db_init_test.sh` shell scripts, which had the
+relationship backwards: the connection string is the adapter's own input
+first, and the shell scripts parse the same string only because the `mysql`
+CLI takes discrete flags rather than a URL.
+
+Special characters in the connection string's user or password must be
+percent-encoded (`@` as `%40`, `#` as `%23`, `/` as `%2F`, …) — mysql2 and
+the init scripts' shell-side URL parsing both percent-decode the userinfo the
+same way, so an unencoded reserved character parses differently, or fails to
+parse, on one side or the other.
+
+## Engine floor: MySQL 8.0.14+
+
+`mysqlAdapter` runs a boot-time `SELECT VERSION()` check against the pool's
+first connection and throws if the server is older than 8.0.14 or is
+MariaDB (MariaDB reports version strings that would otherwise satisfy the
+numeric floor, so it is rejected explicitly by name — see
+`src/lib/boot-check.ts`). A too-old server or MariaDB is a configuration
+error, so the check fails fast at `initBylineCore()` boot rather than
+surfacing later as an obscure SQL error the first time a query needs a
+feature the server doesn't have.
+
+8.0.14 is not an arbitrary floor — it is the first MySQL release with two
+features this adapter's storage layer depends on:
+
+- **`LEFT JOIN LATERAL`**, used for the field-level sort path in
+  `findDocuments`.
+- **Subqueries in a view's `FROM` clause**, which MySQL forbade before
+  8.0.14. Both current-version views
+  (`byline_current_documents`, `byline_current_published_documents`) resolve
+  the current version per document via a `ROW_NUMBER() OVER (PARTITION BY
+  document_id)` window inside a derived table in their `FROM` clause — the
+  same shape as the Postgres adapter's views — so this restriction, not the
+  `LATERAL` requirement, is the adapter's real engine floor.
+
+MariaDB is out of scope for this release: it lacks `LATERAL` joins, so
+supporting it would need a correlated-subquery rewrite of the field-sort
+path. Tracked as
+[on-demand follow-up work](https://github.com/Byline-CMS/bylinecms.dev/issues/54)
+if you need it sooner than "on demand."
+
+## UUID and timestamp conventions
+
+- **Ids are `CHAR(36) CHARACTER SET ascii COLLATE ascii_bin`** — canonical
+  UUID text, compared byte-wise rather than under an accent- or
+  case-folding collation. Every id and foreign-key column in the schema
+  uses this type. Ids are always app-generated UUIDv7 (the `uuid` package's
+  `v7()`), never database-generated — UUIDv7's canonical text form is
+  time-ordered, so `ORDER BY id DESC` version resolution works the same way
+  it does on the numeric-friendly ids some other schemas use.
+- **Audit timestamps are `DATETIME(6)`** (microsecond precision), matching
+  the Postgres adapter's `timestamp(name, { precision: 6, withTimezone: true })`
+  convention exactly. Every table's `created_at` / `updated_at` uses this
+  shape. `TIMESTAMP` (MySQL's other temporal type) is not used anywhere in
+  this schema — its year-2038 range limit makes it unsuitable for an
+  audit trail with no defined retention horizon.
+- **Every `DATETIME` column is UTC by convention.** MySQL's `DATETIME` type
+  carries no time zone identity the way Postgres's `TIMESTAMPTZ` does, so
+  UTC discipline is enforced entirely at the connection layer: the mysql2
+  pool is opened with `timezone: 'Z'`, which stops the driver from
+  reinterpreting stored UTC values against the server's or session's local
+  time zone on the way in or out.
+- **`document_paths.path` is pinned `utf8mb4_bin`** rather than the
+  database's default collation, so path lookups compare bytes exactly and
+  agree with the Postgres adapter's default (accent- and case-sensitive)
+  comparison — see "Differences from the Postgres adapter" below for why
+  this column needed a deliberate override.
+
+## Counters emulation
+
+MySQL has no `CREATE SEQUENCE`. Byline's counter groups (used for
+per-installation and per-scope sequential numbering) are emulated with a
+registry table, `byline_counter_groups`, that **is** the allocator rather
+than a wrapper around a database sequence object: `current_value` holds the
+counter's live state, and each allocation issues an atomic
+`UPDATE`/`INSERT ... ON DUPLICATE KEY UPDATE` followed by a same-connection
+`SELECT LAST_INSERT_ID()` to read back the value it just set — the classic
+`LAST_INSERT_ID(expr)` idiom, requiring no separate `SELECT ... FOR UPDATE`
+round trip. Because `LAST_INSERT_ID()` is per-connection session state, the
+two-statement sequence is issued over a single checked-out pool connection
+rather than through `pool.query()` directly, which could otherwise hand the
+two statements to two different physical connections and return the wrong
+session's value. See `src/modules/counters/counters-commands.ts` for the
+full implementation.
+
+## Differences from the Postgres adapter
+
+Both adapters implement the same storage model and pass the same
+`@byline/db-conformance` suite, but MySQL and Postgres are different
+databases, and a few divergences are real rather than papered over.
+
+- **`LIKE` is case- *and* accent-insensitive**, unlike Postgres's `ILIKE`,
+  which is case-insensitive only. Store *value* columns keep the database's
+  default collation, `utf8mb4_0900_ai_ci` (`ai` = accent-insensitive, `ci` =
+  case-insensitive), so a `query` search against `store_text` values will
+  match `café` when searching `cafe`, and `Café` when searching `cafe`,
+  where the same search against the Postgres adapter would match neither.
+  This is a deliberate, spec-elected divergence, not an oversight — see
+  `packages/db-mysql/src/database/schema/common.ts`'s `varcharCaseSensitive`
+  docblock for the evidence that ruled it in. The one place this divergence
+  is *not* allowed to stand is `byline_document_paths.path`: that column is
+  pinned to `utf8mb4_bin` (byte-exact) instead, so `/About` and `/about`
+  remain two distinct paths on both adapters, and so combining marks that
+  are meaning-bearing in some scripts (a Thai tone mark, a Devanagari
+  anusvara, Hebrew niqqud) are never silently folded together the way
+  `ai_ci` would fold them.
+- **No search provider yet.** `@byline/search-postgres` has no MySQL
+  counterpart today — a collection's `search` config
+  (`CollectionDefinition.search`) requires a registered `SearchProvider`,
+  and none ships for MySQL yet. Track
+  [the `@byline/search-mysql` follow-up issue](https://github.com/Byline-CMS/bylinecms.dev/issues/52)
+  for status.
+- **The connection string is the only connection input.** See "Usage"
+  above — this is called out here too because it is the most common way
+  this adapter is misconfigured by a reader coming from the Postgres
+  adapter's `.env.example`, which historically documented the same shape
+  for a different reason.
+- **Temporal field values.** As of this release both adapters return `date`
+  and `datetime` field values as `Date` objects (`date` anchored to UTC
+  midnight for its calendar day; `time` remains a string on both adapters).
+  This adapter always returned `Date` here; the Postgres adapter converged
+  onto the same shape in this release. See the changeset for what a
+  consumer upgrading `@byline/db-postgres` needs to check.
+
+## Search on MySQL
+
+There is no MySQL search provider yet, and the absence is load-bearing rather
+than cosmetic: `validateSearchConfig` runs inside `initBylineCore()` and
+**throws** when any collection declares a `search` block but no provider is
+registered. Byline's own reference application opts five collections into
+search, so a MySQL installation that copies it fails at boot with an error that
+does not mention MySQL at all.
+
+Until `@byline/search-mysql` exists, register a no-op provider. It satisfies
+validation, and indexing and querying become silent no-ops rather than errors —
+the admin Reindex action and any search page return nothing, which is the honest
+answer on this adapter today:
+
+```ts
+const noopSearch = {
+  capabilities: {
+    facets: false,
+    typoTolerance: false,
+    semantic: false,
+    bm25: false,
+    weighting: false,
+    highlights: false,
+  },
+  async upsert() {},
+  async remove() {},
+  async search() {
+    return { hits: [], total: 0 }
+  },
+}
+
+await initBylineCore({
+  // …
+  db,
+  search: noopSearch,
+})
+```
+
+The alternative — removing the `search` block from every collection definition —
+also works, but it discards configuration you will want back when a provider
+lands. The no-op keeps your collections declarative and confines the workaround
+to one place.
+
+## Not yet shipped
+
+- **`@byline/search-mysql`** — see [Search on MySQL](#search-on-mysql) above.
+  Tracked in [issue #52](https://github.com/Byline-CMS/bylinecms.dev/issues/52).
+- **CLI support.** `byline init` scaffolds a Postgres installation. Adding MySQL
+  to an existing project is a manual edit to `byline/server.config.ts` — swap
+  `pgAdapter` for `mysqlAdapter`, swap the `@byline/db-postgres/admin` import for
+  `@byline/db-mysql/admin`, drop the `@byline/search-postgres` migrate call, and
+  register the no-op search provider above.
+- **A MySQL storage-benchmark target.** The design spec flags view
+  materialisation (the `ROW_NUMBER()` window inside a derived table, used
+  by both current-version views) as a question to answer before this
+  adapter's GA — Postgres's own benchmark sweep
+  ([`docs/03-architecture/01-document-storage.md`](https://github.com/Byline-CMS/bylinecms.dev/blob/develop/docs/03-architecture/01-document-storage.md#indicative-benchmarks))
+  has no MySQL counterpart yet. Tracked in
+  [issue #53](https://github.com/Byline-CMS/bylinecms.dev/issues/53).
+- **MariaDB support** — see "Engine floor" above. Tracked in
+  [issue #54](https://github.com/Byline-CMS/bylinecms.dev/issues/54).
+
+## License
+
+MPL-2.0