Pull Request Checklist

• Have you added new tests to prevent regressions?
• If a documentation update is necessary, have you opened a PR to the documentation repository?
• Did you update the typescript typings accordingly (if applicable)?
• Does the description below contain a link to an existing issue or a description of the issue you are solving?
• Does the name of your PR follow our conventions?

Description of Changes

Stacked on #18328 (needs mariadb >= 3.5.0, see below).

The bug

handleJsonSelectQuery walked the model's JSON attributes and the result set's column metadata with the same index:

for (const [i, _field] of Object.keys(this.model.fieldRawAttributesMap).entries()) {
  // ...
  (!meta[i] || meta[i].dataTypeFormat !== 'json')

The metadata follows the order of the SELECT clause, which has no relation to the order of the model's attributes. Any model with more than one JSON attribute could therefore read the wrong column's metadata and either skip decoding a value it should have decoded, or try to decode one the driver had already decoded.

The fix

Match the metadata by column instead:

• name() is the alias the column has in the result set, which is what the row is keyed by, so it is the only unambiguous match.
• orgName() is only a fallback for aliased columns, and is qualified by orgTable() so an include cannot match a same-named column of a joined table.

The migration to the driver's public isDataTypeFormatJson() accessor is not part of this PR — that is dependency catch-up for the mariadb 3.5 bump and lives in #18328, which is also what turns mariadb latest green there. This PR is only the matching bug, which is pre-existing and independent of the driver version.

Cleanup included

The rows were being run through Array#map whose result was assigned to a local and then dropped, so only the in-place mutation ever had an effect. The DataTypes.JSON.parse branch inside it was dead — that static does not exist (verified at runtime: typeof DataTypes.JSON.parse === 'undefined'). Had it ever been defined, the map would have replaced each row with a single parsed field value.

Decoding now happens in place, and the loop-invariant metadata check is hoisted out of the row loop. handleJsonSelectQuery is marked @internal so it stays out of the generated API docs.

Tests

packages/mariadb/src/query.test.ts covers metadata matched by column rather than by attribute position, the json-format guard, the aliased-column fallback and its table qualification, the no-metadata case, and non-model queries. 10 tests, all passing.

🤖 Generated with Claude Code

https://claude.ai/code/session_01EgPPfqYYk6PFGbanp5mAFh