SQL¶
The path most callers use: connect once, configure a policy once, hand the agent a tool.
Connecting¶
gantry.sql.connect
¶
connect(
provider: str,
*,
policy: Policy | None = None,
**config: object,
) -> SQLConnection
Resolve a provider preset and create a governed SQL connection.
policy attaches a reusable policy to everything this connection runs. It
is trusted configuration: per-operation constraints still apply on top, and
neither can be reached from a tool argument.
Source code in gantry/sql/api.py
484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 | |
gantry.sql.SQLConnection
¶
A provider-neutral, governed SQL connection.
Configuration and the native adapter remain private so an agent tool cannot accidentally expose credentials or a raw database connection.
Source code in gantry/sql/api.py
55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 | |
policy
property
¶
policy: Policy | None
The reusable policy this connection admits against, if any.
Readable so an application can log what it attached. There is no setter: policy is configuration, and something that could be swapped at runtime is something an agent-reachable code path could swap.
capabilities
¶
capabilities() -> SQLCapabilities
Return the adapter's declared SQL capabilities without credentials.
Source code in gantry/sql/api.py
93 94 95 96 | |
describe
async
¶
describe() -> DatabaseSchema
Return normalized catalogs, schemas, tables, and columns.
Source code in gantry/sql/api.py
98 99 100 101 102 103 | |
query
¶
query(
*,
read_only: bool = True,
schemas: Sequence[str] = (),
tables: Sequence[str] = (),
denied_tables: Sequence[str] = (),
max_rows: int = 1000,
timeout: float = 30,
max_bytes_scanned: int | None = None,
max_cost_usd: float | None = None,
allow_multiple_statements: bool = False,
checks: Sequence[Verifier | MaterializationCheck] = (),
verify: Sequence[Verifier | MaterializationCheck]
| None = None,
) -> SQLQuery
Configure a governed query operation.
checks takes the same gantry.verify checks a materialization takes,
evaluated against the rows the query returns rather than a destination,
plus any Verifier that inspects the execution itself.
Source code in gantry/sql/api.py
162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 | |
result
async
¶
result(handle: ExecutionHandle) -> SQLResult
Recover a completed result directly from its provider-native handle.
Source code in gantry/sql/api.py
357 358 359 360 361 362 363 | |
wait
async
¶
wait(
handle: ExecutionHandle,
*,
poll_interval_seconds: float = 1.0,
) -> SQLResult
Observe a submitted job and recover its result, including after reconnect.
Source code in gantry/sql/api.py
365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 | |
materialize
¶
materialize(
*,
sources: Sequence[str] = (),
destinations: Sequence[str],
create_only: bool = True,
max_bytes_scanned: int | None = None,
max_cost_usd: float | None = None,
timeout: float = 300,
checks: Sequence[MaterializationCheck] = (),
verify: Sequence[MaterializationCheck] | None = None,
) -> SQLMaterializer
Configure a governed, create-only native SQL materialization operation.
Source code in gantry/sql/api.py
409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 | |
Configuring an operation¶
gantry.sql.SQLQuery
dataclass
¶
A query policy configured once for direct calls or agent tools.
Source code in gantry/sql/query.py
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 | |
tool
¶
tool(
*,
name: str = "query_sql",
description: str = "Run a governed read-only SQL query.",
) -> Tool[Run]
Return the narrow framework-neutral form of this query operation.
Source code in gantry/sql/query.py
56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 | |
gantry.sql.SQLPolicy
dataclass
¶
The bounds application code puts around agent-written SQL.
Defaults are the safe end: read-only, 1,000 rows, 30 seconds, one
statement. An empty allowed_schemas/allowed_tables means no allow-list
is applied, while denied_tables always wins. Names are lower-cased and
frozen at construction, and a malformed policy raises there rather than at
submission — passing a bare string where a collection belongs is a
TypeError, not a policy that matches one table.
Declaring a field is not the same as it being enforced: a bound is admitted only when the adapter can apply it.
Source code in gantry/sql/policy.py
8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 | |
A policy is a claim about what the adapter will enforce
Declaring a field is not the same as it being enforced. read_only=True is
admitted only when the adapter can hold a read-only session in the engine;
a row limit is admitted only when the adapter can bound the result. See the
capability matrix for which provider enforces what, and
what happens when it cannot.
Materialization¶
Create-only: one CREATE TABLE AS or CREATE VIEW AS, to a schema-qualified
destination that does not already exist.
gantry.sql.SQLMaterializer
¶
Credential-free, create-only SQL materializer.
Source code in gantry/sql/materialization.py
321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 | |
tool
¶
tool(
*,
name: str = "materialize_sql",
description: str = "Create a derived table from approved SQL sources.",
) -> Tool[Run]
Return the narrow framework-neutral form of this operation.
Source code in gantry/sql/materialization.py
370 371 372 373 374 375 376 377 378 379 380 381 382 383 | |
gantry.sql.MaterializationPolicy
dataclass
¶
Where a materialization may read from and write to.
destinations must be non-empty — there is no default place to write — and
patterns are fnmatch-style, lower-cased at construction. create_only is
fixed at True in v0 and passing anything else raises, so replacement
cannot be enabled by a config change before the semantics exist.
Source code in gantry/sql/materialization.py
212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 | |
gantry.sql.MaterializationResult
dataclass
¶
The outcome of a materialization: the destination, and whether to trust it.
ok is ACCEPTED only, which requires verification to have passed — a
CREATE TABLE AS that ran and produced the wrong table is not accepted.
uri names the destination when one was created.
Source code in gantry/sql/materialization.py
263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 | |
evidence
class-attribute
instance-attribute
¶
evidence: EvidenceBundle | None = None
What Gantry observed while deciding, serializable and outliving the run.
gantry.sql.MaterializationError
¶
Bases: Exception
Raised when a proposal is refused, carrying why and at what stage.
failure is the normalized reason and status the outcome it maps to,
defaulting to REJECTED — the common case, where nothing ran. It is an
exception rather than a returned value because a refused proposal has no
result to describe.
Source code in gantry/sql/materialization.py
295 296 297 298 299 300 301 302 303 304 305 306 307 | |
Parsing a proposal¶
What turns proposed SQL into something checkable. Call these directly to inspect what a statement would do before submitting it.
gantry.sql.parse_materialization
¶
parse_materialization(sql: str) -> MaterializationPlan
Parse caller-proposed SQL into a create-only MaterializationPlan.
Accepts exactly one CREATE TABLE ... AS or CREATE VIEW ... AS whose
destination names a schema, and returns the operation, the schema-qualified
destination, and the source tables the body reads. Raises
MaterializationError for anything else: several statements, a non-create
operation, OR REPLACE or IF NOT EXISTS, an unqualified destination, a
body that is not a SELECT/WITH query, or a body carrying a second
effect such as DELETE or DROP.
Source code in gantry/sql/materialization.py
884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 | |
gantry.sql.MaterializationProposal
dataclass
¶
Caller-proposed SQL before anything has been checked about it.
Construction only rejects a non-string or blank submission; the naming is
the point — what arrives here is a proposal, and it is a plan only after
parse_materialization has accepted it.
Source code in gantry/sql/materialization.py
121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 | |
gantry.sql.MaterializationPlan
dataclass
¶
What a proposal turned out to be: one create, its destination, sources.
Returned by parse_materialization and checked against
MaterializationPolicy. sources is what the body reads, excluding CTE
names, so the policy matches real tables rather than local aliases.
Source code in gantry/sql/materialization.py
139 140 141 142 143 144 145 146 147 148 149 150 151 | |
gantry.sql.MaterializationOperation
¶
Bases: StrEnum
The two operations v0 materialization allows.
Both create; neither replaces. A destination that already exists is a refusal rather than an overwrite.
Source code in gantry/sql/materialization.py
84 85 86 87 88 89 90 91 92 | |
gantry.sql.TableRef
dataclass
¶
A table name parsed out of a materialization, with its parts kept.
qualified_name joins whichever of catalog, schema and name are present.
Materialization requires a schema on the destination, so that an agent
cannot write to whatever the session's search path happens to be.
Source code in gantry/sql/materialization.py
95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 | |
Schema and classification¶
gantry.sql.DatabaseSchema
dataclass
¶
What the connection can see, as the schema handed to an agent.
Produced by SQLConnection.describe(). This is the right shape to put in a
prompt: only what the credential can reach, so the agent is not invited to
reference a table it cannot read.
Source code in gantry/sql/schema.py
39 40 41 42 43 44 45 46 47 48 49 50 51 | |
gantry.sql.Table
dataclass
¶
One table or view, with the columns an agent may write SQL against.
kind distinguishes a table from a view. columns is empty when the
adapter listed the table without describing it.
Source code in gantry/sql/schema.py
22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 | |
gantry.sql.Column
dataclass
¶
One column as the engine reports it.
type is the engine's own type name, not a normalized one: an agent
writing SQL needs the name the engine will accept.
Source code in gantry/sql/schema.py
8 9 10 11 12 13 14 15 16 17 18 19 | |
gantry.sql.SQLClassification
dataclass
¶
The structure a policy check runs against, never a transpilation.
read_only is the field most decisions turn on, and it is deliberately
conservative: a statement must be recognizably read-only to be treated as
such. tables is everything referenced, write_targets only what is
written, so a policy can allow reading a table it forbids writing.
A SELECT is not automatically a read. SELECT ... FOR UPDATE takes row
locks and SELECT nextval(...) advances a sequence, both of which
PostgreSQL refuses in a read-only transaction. When operation is SELECT
and read_only is false, read_only_reason says which of those it was, so
a refusal can explain itself instead of reporting that a SELECT is not
allowed by a read-only policy.
Source code in gantry/sql/classification.py
58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 | |
gantry.sql.SQLOperation
¶
Bases: StrEnum
What a statement does, at the granularity policy decisions need.
MULTI_STATEMENT is its own operation rather than a list, because a batch
is refused as a batch unless the policy allows several statements.
UNKNOWN is deny-by-default: an unclassifiable statement is not a
SELECT.
Source code in gantry/sql/classification.py
8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 | |
gantry.sql.SQLObjectRef
dataclass
¶
A possibly-qualified reference to a table as it appeared in the SQL.
schema and catalog are None when the statement did not qualify the
name; qualified_name joins whichever parts are present. Policy matching
compares against these names, so an unqualified reference is matched as
written rather than silently resolved.
Source code in gantry/sql/classification.py
27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 | |
gantry.sql.ParsedSQL
dataclass
¶
The statements a dialect found in one submitted string.
Splitting is the step that makes "one statement" checkable. Anything that yields more than one statement is a multi-statement submission, whatever it looked like to the caller.
Source code in gantry/sql/classification.py
46 47 48 49 50 51 52 53 54 55 | |
gantry.sql.ExplainResult
dataclass
¶
What the engine's planner estimated, before anything ran.
supported is false when the engine cannot explain the statement, which is
distinct from an estimate of zero: a byte-scanned bound cannot be enforced
on an estimate that does not exist. Every estimate is optional for the same
reason.
Source code in gantry/sql/explain.py
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 | |
Extending¶
gantry.sql.register_provider
¶
register_provider(
name: str,
*,
dialect: str,
driver: str,
adapter_factory: AdapterFactory,
validate_config: ConfigValidator | None = None,
metadata: Mapping[str, object] | None = None,
replace: bool = False,
) -> None
Register a provider that gantry.sql.connect can open by name.
adapter_factory is called with the resolved SQLTarget each time a
connection is opened, so one provider can serve many targets.
validate_config runs before the factory and should raise on
configuration the adapter cannot honour. Raises ValueError if the name
is empty, or already registered and replace is false.
Source code in gantry/sql/registry.py
39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 | |
gantry.sql.providers
¶
Built-in SQL provider presets.
gantry.sql.SQLAdapter
¶
Bases: Protocol
The contract a SQL backend implements to be governed by Gantry.
Declare what you can enforce (capabilities), expose the schema
(describe), ask the engine to check and estimate a statement (validate,
explain), then run and track it (submit, status, result, cancel).
A capability you do not declare is a bound Gantry will refuse to promise,
so under-declaring is safe and over-declaring is not.
Source code in gantry/sql/adapter.py
16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 | |
gantry.sql.SQLCapabilities
dataclass
¶
What one SQL adapter can enforce, declared per provider.
The source of truth behind the published
capability matrix: core_capabilities() projects
these onto the engine-neutral AdapterCapabilities that admission checks,
and policy_requirements() derives what a given SQLPolicy demands. Note
write_execution defaults to true while everything else defaults to false —
a new adapter is assumed able to write and assumed unable to bound.
Source code in gantry/sql/capabilities.py
11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 | |
gantry.sql.MaterializationAdapter
¶
Bases: Protocol
Additional adapter operation required only for materialization.
inspect_table is how create-only is enforced and how the destination is
verified afterwards: returning None for a table that does not exist is
what distinguishes "not created" from "created empty". An adapter without
this cannot materialize.
Source code in gantry/sql/materialization.py
173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 | |
gantry.sql.MaterializationCapabilities
dataclass
¶
What an adapter can enforce for materialization specifically.
Separate from SQLCapabilities because materialization needs guarantees a
query does not: destination_introspection is what makes create-only
checkable, and without it the destination cannot be verified after the job
runs. All default to false.
Source code in gantry/sql/materialization.py
154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 | |
gantry.sql.SQLTarget
dataclass
¶
A resolved connection target: the provider, its dialect, and its config.
Built by connect from a registered provider. It holds credentials, so it
stays in application code — what reaches the engine adapter is this, and
what reaches the agent is only the tool schema.
Source code in gantry/sql/target.py
8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 | |
gantry.sql.register
¶
register(
name: str,
*,
adapter: SQLAdapter,
dialect: str,
driver: str | None = None,
replace: bool = False,
) -> None
Register a single already-built adapter as a provider named name.
A shorthand over register_provider for tests and embedded adapters: every
target resolved through this name shares the one adapter instance. driver
defaults to name.
Source code in gantry/sql/registry.py
72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 | |
Dialects¶
A dialect decides how a submission is split and classified. It never rewrites SQL — what the caller wrote is what the engine receives.
gantry.sql.SQLDialect
¶
Bases: Protocol
How one SQL dialect is split and classified for policy checks.
Three methods, none of which rewrite SQL: parse splits a submission into
statements, classify says what the single statement does, and
referenced_objects lists the tables it names. Register an implementation
with register_dialect; ConservativeDialect is the deny-by-default
fallback.
Source code in gantry/sql/dialect.py
51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 | |
gantry.sql.ConservativeDialect
¶
A small deny-by-default classifier shared until a dialect overrides it.
The two options are lexical rules that genuinely differ between engines, and
getting them wrong changes where a statement ends. backslash_escapes is
off by default, matching PostgreSQL with standard_conforming_strings,
where a backslash is only special inside an E'' string. dollar_quoting
is on by default because PostgreSQL has it and MySQL does not — there, $$
is a syntax error and $ is an ordinary identifier character.
Source code in gantry/sql/dialect.py
68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 | |
gantry.sql.MySQLDialect
¶
Bases: ConservativeDialect
ConservativeDialect with MySQL's lexical rules rather than PostgreSQL's.
Two differences, both of which move where a statement ends. MySQL escapes
backslashes inside ordinary strings — NO_BACKSLASH_ESCAPES is not in the
default sql_mode — so 'a\'; SELECT 2' is one string and one statement.
Reading it with PostgreSQL's rule splits it in two and refuses it as a
batch, which is safe but wrong. And MySQL has no dollar-quoting: $$ is a
syntax error there, while $ is an ordinary identifier character, so
my$tab$le is one name.
Checked against MySQL 8.4 with the default sql_mode.
Source code in gantry/sql/dialect.py
179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 | |
gantry.sql.register_dialect
¶
register_dialect(
name: str, dialect: SQLDialect, *, replace: bool = False
) -> None
Register a SQL dialect under a name, for classification and splitting.
Source code in gantry/sql/registry.py
29 30 31 32 33 34 35 36 | |