jade-sql 0.7.0 → 0.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 82ae87a5571e7ef32804036dd347134fc11bcf20a66ebabe7562ac898f943262
-  data.tar.gz: c81268fa4accc4f8bb8f945a8ba164a64ac0ca629d554c9d99874ecb4fb697d5
+  metadata.gz: 8a1a8c1496c50e9d5ddc41779759904608bd05c8b92a19e2c7a4be8434d0c0af
+  data.tar.gz: 4dae8fec72bcf27bf3f0dca7de137173e0edc96cdeefe4423be258f04862ea4a
 SHA512:
-  metadata.gz: c1cbadd648ec547bcd888c79504d40b630b7e808f0ef0b1e0f379d8b581816d1c3110112fbed3b597dae9987270b13082e68b0561a6ea5bfec2637e7fc81bc4d
-  data.tar.gz: 2864083ceebdd23042ddcd31a3c81d2446b1533b5a7ba8614565138899de6d8fea76bb6a485a8781d16315174cf1856f989890664157bb371ab56cfae2a4e63f
+  metadata.gz: b82de8f2b0d3b8286235a6387aed031c32df9303ea7adc7ae1413f402d328fa7da8a6bd9262ba188c3920b6a79409c4fd597cc4250ed356f5304cc4a19ca0b11
+  data.tar.gz: d65bea1279860d61c7c1d321fdaf3c352797bf0470a124ade49769fc697c745053d417d535ee394329f6fea003857d391bcf98df9d199a01269d095a21bac219

data/README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/agustinrhcp/jade-sql/actions/workflows/ci.yml/badge.svg)](https://github.com/agustinrhcp/jade-sql/actions/workflows/ci.yml)
 
-Type-safe SQL for Jade. Builds queries and mutations from a generated
+Type-safe SQL for Jade. Builds queries and writes from a generated
 schema, renders them to `(String, List(Value))`, and runs them against
 ActiveRecord via a Task port that auto-decodes rows into typed Jade
 structs.
@@ -24,22 +24,28 @@ To execute queries at runtime, opt into the AR-backed task port:
 require 'jade-sql/runtime'
 ```
 
-To get the rake task for schema generation:
+To get the rake tasks for schema generation:
 
 ```ruby
 # Rakefile (or lib/tasks/jade.rake)
 load Gem.find_files('jade-sql/tasks.rake').first
 ```
 
+`rake jade:schema` writes the schema; `rake jade:schema:check` fails when the
+checked-in one no longer matches `db/structure.sql`, which is what a migration
+merged without regenerating looks like. Both are also `jade-sql schema` and
+`jade-sql schema --check`.
+
 ## At a glance
 
 Generate a typed schema from `db/structure.sql`, then build a query against
-it. The result is a `Q` you render with `to_sql` or run with `fetch_*`; rows
+it. The result is a `Query` you render with `to_sql` or run with `fetch_*`; rows
 decode straight into your struct.
 
 ```jade
-import Sql exposing (Selector, eq, to_expr)
-import Sql.Query exposing (Q, field, from, join, select, where)
+import Sql exposing (Selector, eq)
+import Sql.Expr as Expr
+import Sql.Query exposing (Query, field, from, join, select, where)
 import Schema exposing (patients, appointments)
 
 struct Visit = {
@@ -47,14 +53,14 @@ struct Visit = {
   reason: String
 }
 
-def scheduled_visits -> Q(Selector(Visit))
+def scheduled_visits -> Select(Visit)
   p <- from(patients)
-  a <- join(appointments, (a) -> { p.id |> eq(a.patient_id) })
+  a <- join(appointments, (a) -> { p.id |> Expr.eq(a.patient_id) })
 
   select(Visit(_, _))
     |> field(p.name)
     |> field(a.reason)
-    |> where(a.status |> eq(to_expr("scheduled")))
+    |> where(a.status |> eq("scheduled"))
 end
 ```
 
@@ -65,6 +71,6 @@ that decodes each row into `Visit`.
 
 - [Building SQL](docs/building.md) — generate a schema, build queries
   (joins, sorting/grouping, pagination, aggregates, arrays, JSONB) and
-  mutations (insert/update/delete, RETURNING, timestamps, UUIDs).
-- [Running queries and mutations](docs/running.md) — `fetch_*` / `execute`,
+  writes (insert/update/delete, RETURNING, timestamps, UUIDs).
+- [Running queries and writes](docs/running.md) — `fetch_*` / `execute`,
   transactions, and testing without a database.