exwiw 1.1.6 → 1.1.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +12 -0
- data/README.md +318 -1017
- data/docs/mongodb.md +4 -0
- data/docs/scope-id-set-join-notes.md +12 -0
- data/lib/exwiw/adapter/mongodb_adapter.rb +12 -0
- data/lib/exwiw/adapter/mysql_adapter.rb +37 -15
- data/lib/exwiw/adapter/mysql_client.rb +33 -2
- data/lib/exwiw/adapter/postgresql_adapter.rb +26 -16
- data/lib/exwiw/adapter/sqlite_adapter.rb +16 -13
- data/lib/exwiw/adapter.rb +30 -1
- data/lib/exwiw/cli.rb +33 -1
- data/lib/exwiw/query_ast.rb +34 -1
- data/lib/exwiw/query_ast_builder.rb +177 -44
- data/lib/exwiw/version.rb +1 -1
- data/lib/exwiw.rb +3 -1
- metadata +2 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: ef76bef2bd961b6bf50afcdd7f28e87e5c78ab587385519bbbfc3d66e3438c6d
|
|
4
|
+
data.tar.gz: 99c7d8cb5250fd3cfb7951a586d575dd76b3dbfa20f6c9aa5125643ce7bd12cb
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 271ef2c7496ab0d6d118a0e27195d0b411f8642914cc0a0eca68abc3d47df02b8876261c40933790f99a637f6e2eb1f63e8fc2ce2f618315151c3622370c7a1a
|
|
7
|
+
data.tar.gz: 356b3c7e579c980a38ab649e2c986bbb33310f4906593ff504f14ed2839f3d3249e60337fe355d8b32ddf2e72e6439b07bfa5da5845d194cceaa2a0d933a21b8
|
data/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,18 @@
|
|
|
2
2
|
|
|
3
3
|
## [Unreleased]
|
|
4
4
|
|
|
5
|
+
## [1.1.8] - 2026-10-29
|
|
6
|
+
|
|
7
|
+
### Added
|
|
8
|
+
|
|
9
|
+
- **`--ssl-mode` and `--ssl-ca` connect to MySQL over TLS.** exwiw passed no TLS options to the driver or to `mysqldump`, so with a client library that does not use TLS by default (MariaDB Connector/C, for one) every command failed against a server with `require_secure_transport=ON` — `Connections using insecure transport are prohibited`. The two options take the MySQL client's values (`disabled`, `preferred`, `required`, `verify_ca`, `verify_identity`) and a CA file, and apply to the `mysql2` / `trilogy` connection and to `mysqldump`; MariaDB's `mysqldump`, which has no `--ssl-mode`, gets the equivalent `--ssl` / `--ssl-verify-server-cert` flags, and where MariaDB's client library or `mysqldump` lacks a mode, `verify_ca` also checks the host name and `preferred` leaves the client default. Without the options nothing changes. mysql adapter only.
|
|
10
|
+
|
|
11
|
+
## [1.1.7] - 2026-10-01
|
|
12
|
+
|
|
13
|
+
### Added
|
|
14
|
+
|
|
15
|
+
- **A narrowed table with a `belongs_to` to itself also keeps the ancestors of its rows.** A self-reference was ignored on every scoping path, so narrowing a tree table such as `categories` (`parent_id → categories.id`) to the categories a tenant's products point at dropped their parent categories and left `parent_id` dangling in the dump. The SQL adapters now wrap such a table's scope in a `WITH RECURSIVE` walk up every non-polymorphic self-reference, whichever path narrowed it. The ancestors are added regardless of the table's `filter` and scope, so where a tree spans tenants the dump includes the other tenant's ancestors. Tables that `belongs_to` the tree follow the rows including the ancestors, so the ancestors' own child rows are kept too — a table whose join route passes through the tree is narrowed by the route's first table's extraction query instead of being joined along it — and a table the tree points at includes the ancestors' references. A table dumped in full and a table extracted with `batch_scope` are unchanged (the latter with a pre-flight warning); the MongoDB adapter adds no ancestors and warns instead. Tables without a self-reference emit the same SQL as before. Requires MySQL 8.0+ for `WITH RECURSIVE`.
|
|
16
|
+
|
|
5
17
|
## [1.1.6] - 2026-09-29
|
|
6
18
|
|
|
7
19
|
### Added
|