pydoptic-sql 0.0.1.post1.dev2__tar.gz → 0.0.2.post1.dev1__tar.gz

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.
Files changed (28) hide show
  1. {pydoptic_sql-0.0.1.post1.dev2/src/pydoptic_sql.egg-info → pydoptic_sql-0.0.2.post1.dev1}/PKG-INFO +5 -4
  2. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/README.md +4 -3
  3. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1/src/pydoptic_sql.egg-info}/PKG-INFO +5 -4
  4. pydoptic_sql-0.0.2.post1.dev1/src/pydoptic_sql.egg-info/scm_version.json +8 -0
  5. pydoptic_sql-0.0.1.post1.dev2/src/pydoptic_sql.egg-info/scm_version.json +0 -8
  6. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/LICENSE +0 -0
  7. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/pyproject.toml +0 -0
  8. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/setup.cfg +0 -0
  9. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql/__init__.py +0 -0
  10. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql/py.typed +0 -0
  11. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql/sql_computed.py +0 -0
  12. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql/sql_constraint.py +0 -0
  13. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql/sql_having.py +0 -0
  14. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql/sql_order.py +0 -0
  15. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql/sql_query.py +0 -0
  16. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql/sql_service.py +0 -0
  17. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql/sql_table.py +0 -0
  18. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql.egg-info/SOURCES.txt +0 -0
  19. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql.egg-info/dependency_links.txt +0 -0
  20. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql.egg-info/requires.txt +0 -0
  21. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql.egg-info/scm_file_list.json +0 -0
  22. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/src/pydoptic_sql.egg-info/top_level.txt +0 -0
  23. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/test/test_sql_computed.py +0 -0
  24. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/test/test_sql_constraint.py +0 -0
  25. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/test/test_sql_having.py +0 -0
  26. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/test/test_sql_params.py +0 -0
  27. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/test/test_sql_query.py +0 -0
  28. {pydoptic_sql-0.0.1.post1.dev2 → pydoptic_sql-0.0.2.post1.dev1}/test/test_sql_service.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: pydoptic-sql
3
- Version: 0.0.1.post1.dev2
3
+ Version: 0.0.2.post1.dev1
4
4
  Summary: A type-safe SQL query builder built on pydoptic
5
5
  Author: John Hungerford
6
6
  License-Expression: MIT
@@ -55,9 +55,8 @@ with psycopg.connect("host=localhost dbname=mydb user=postgres password=password
55
55
  print(Worker.name.get_val_safe(worker))
56
56
  ```
57
57
 
58
- Joining a second table narrows and widens the query's type together -- `Constraint2` (not
59
- `Constraint`) is required for a WHERE/ON clause once a second table is in scope, and can reference
60
- either table directly:
58
+ Joining a second table generates a new query with two table type parameters. Constraints added to this
59
+ query are widened to include both table properties (e.g., `Constraint2` instead of `Constraint`):
61
60
 
62
61
  ```python3
63
62
  class Department(SqlTable):
@@ -71,5 +70,7 @@ query = SqlQuery.from_table(Worker).join_inner(
71
70
  ).select(Worker.name, Department.name).where(Constraint2.gte(Worker.age, 18))
72
71
  ```
73
72
 
73
+ Currently, queries can include joins up to four tables deep.
74
+
74
75
  See the [pydoptic README](https://github.com/johnhungerford/pydoptic/tree/main/packages/pydoptic) for
75
76
  the underlying `Prop`/`Select` model this is built on.
@@ -37,9 +37,8 @@ with psycopg.connect("host=localhost dbname=mydb user=postgres password=password
37
37
  print(Worker.name.get_val_safe(worker))
38
38
  ```
39
39
 
40
- Joining a second table narrows and widens the query's type together -- `Constraint2` (not
41
- `Constraint`) is required for a WHERE/ON clause once a second table is in scope, and can reference
42
- either table directly:
40
+ Joining a second table generates a new query with two table type parameters. Constraints added to this
41
+ query are widened to include both table properties (e.g., `Constraint2` instead of `Constraint`):
43
42
 
44
43
  ```python3
45
44
  class Department(SqlTable):
@@ -53,5 +52,7 @@ query = SqlQuery.from_table(Worker).join_inner(
53
52
  ).select(Worker.name, Department.name).where(Constraint2.gte(Worker.age, 18))
54
53
  ```
55
54
 
55
+ Currently, queries can include joins up to four tables deep.
56
+
56
57
  See the [pydoptic README](https://github.com/johnhungerford/pydoptic/tree/main/packages/pydoptic) for
57
58
  the underlying `Prop`/`Select` model this is built on.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: pydoptic-sql
3
- Version: 0.0.1.post1.dev2
3
+ Version: 0.0.2.post1.dev1
4
4
  Summary: A type-safe SQL query builder built on pydoptic
5
5
  Author: John Hungerford
6
6
  License-Expression: MIT
@@ -55,9 +55,8 @@ with psycopg.connect("host=localhost dbname=mydb user=postgres password=password
55
55
  print(Worker.name.get_val_safe(worker))
56
56
  ```
57
57
 
58
- Joining a second table narrows and widens the query's type together -- `Constraint2` (not
59
- `Constraint`) is required for a WHERE/ON clause once a second table is in scope, and can reference
60
- either table directly:
58
+ Joining a second table generates a new query with two table type parameters. Constraints added to this
59
+ query are widened to include both table properties (e.g., `Constraint2` instead of `Constraint`):
61
60
 
62
61
  ```python3
63
62
  class Department(SqlTable):
@@ -71,5 +70,7 @@ query = SqlQuery.from_table(Worker).join_inner(
71
70
  ).select(Worker.name, Department.name).where(Constraint2.gte(Worker.age, 18))
72
71
  ```
73
72
 
73
+ Currently, queries can include joins up to four tables deep.
74
+
74
75
  See the [pydoptic README](https://github.com/johnhungerford/pydoptic/tree/main/packages/pydoptic) for
75
76
  the underlying `Prop`/`Select` model this is built on.
@@ -0,0 +1,8 @@
1
+ {
2
+ "tag": "0.0.2",
3
+ "distance": 1,
4
+ "node": "ga0068181cb2d8dfd1b14469d4ad3bdc4cfd63617",
5
+ "dirty": false,
6
+ "branch": "main",
7
+ "node_date": "2026-08-18"
8
+ }
@@ -1,8 +0,0 @@
1
- {
2
- "tag": "0.0.1",
3
- "distance": 2,
4
- "node": "gf2a88e816d5622e7cf652ca9af0f07673483e3a0",
5
- "dirty": false,
6
- "branch": "main",
7
- "node_date": "2026-08-18"
8
- }