sqlquality 0.4.0__tar.gz → 0.4.1__tar.gz

{sqlquality-0.4.0 → sqlquality-0.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: sqlquality
-Version: 0.4.0
+Version: 0.4.1
 Summary: Measure dbt model performance and complexity, and gate changes on the delta.
 Project-URL: Homepage, https://github.com/hanslemm/sqlquality
 Project-URL: Issues, https://github.com/hanslemm/sqlquality/issues

{sqlquality-0.4.0 → sqlquality-0.4.1}/src/sqlquality/__init__.py

@@ -1,3 +1,3 @@
 """sqlquality — measure dbt model performance and complexity."""
 
-__version__ = "0.4.0"
+__version__ = "0.4.1"

{sqlquality-0.4.0 → sqlquality-0.4.1}/tests/test_workload_redaction.py

@@ -16,7 +16,7 @@ runner = CliRunner()
 #: Distinctive strings that must never appear downstream.
 #:
 #: Be honest about which of these currently discriminate. Measured by disabling
-#: `redact_tree` and sweeping every surface: only `hans@betterdoc.de` leaks, because it
+#: `redact_tree` and sweeping every surface: only `someone@example.com` leaks, because it
 #: is the only one reaching ADV005's evidence — the single proposal type that copies query
 #: text into output. The other three enter via HOT_QUERY, whose proposals carry column
 #: names, roles and counts but never `stat.sql`, so they cannot leak today whatever
@@ -25,15 +25,15 @@ runner = CliRunner()
 #: They stay in the list deliberately, as regression insurance against a future proposal
 #: type that widens what evidence carries. But they are future-proofing, not live
 #: trip-wires, and a reader should not mistake four passing checks for four proofs.
-SECRETS = ("patient-4711", "hans@betterdoc.de", "DE89370400440532013000", "1990-04-17")
+SECRETS = ("ticket-4711", "someone@example.com", "DE89370400440532013000", "2001-02-03")
 
 HOT_QUERY = (
     "select id, note from orders "
     "where status = 'shipped' "
-    "and customer_email = 'hans@betterdoc.de' "
-    "and reference = 'patient-4711' "
+    "and customer_email = 'someone@example.com' "
+    "and reference = 'ticket-4711' "
     "and iban = 'DE89370400440532013000' "
-    "and created_at > '1990-04-17' "
+    "and created_at > '2001-02-03' "
     "order by created_at desc"
 )
 
@@ -57,8 +57,8 @@ HOT_QUERY = (
 #: `--keep-literals` test below is the canary that will tell you: it asserts a secret *is*
 #: retained with the opt-in, which can only hold if some output surface actually carries
 #: query text. If that test starts failing, this scenario has gone vacuous.
-LIKE_QUERY = "select note from orders where note like '%hans@betterdoc.de%'"
-STAR_QUERY = "select * from wide_events where actor_email = 'hans@betterdoc.de'"
+LIKE_QUERY = "select note from orders where note like '%someone@example.com%'"
+STAR_QUERY = "select * from wide_events where actor_email = 'someone@example.com'"
 
 COLUMNS = [
     ("public", "orders", "id", "integer"),
@@ -182,4 +182,4 @@ def test_keep_literals_is_the_only_way_to_retain_values(stubbed):
     payload = json.loads(result.stdout)
     assert payload["redacted"] is False
     # With the opt-in, values are retained — proving the default was doing real work.
-    assert "hans@betterdoc.de" in json.dumps(payload)
+    assert "someone@example.com" in json.dumps(payload)