pytrilogy 0.0.1.102__tar.gz

pytrilogy-0.0.1.102/LICENSE.md

@@ -0,0 +1,19 @@
+Copyright (c) 2023
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

pytrilogy-0.0.1.102/PKG-INFO

@@ -0,0 +1,277 @@
+Metadata-Version: 2.1
+Name: pytrilogy
+Version: 0.0.1.102
+Summary: Declarative, typed query language that compiles to SQL.
+Home-page: 
+Author: 
+Author-email: preql-community@gmail.com
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE.md
+Requires-Dist: lark
+Requires-Dist: jinja2
+Requires-Dist: sqlalchemy<2.0.0
+Requires-Dist: networkx
+Requires-Dist: pyodbc
+Requires-Dist: pydantic
+Requires-Dist: duckdb-engine
+Provides-Extra: postgres
+Requires-Dist: psycopg2-binary; extra == "postgres"
+Provides-Extra: bigquery
+Requires-Dist: sqlalchemy-bigquery; extra == "bigquery"
+Provides-Extra: snowflake
+Requires-Dist: snowflake-sqlalchemy; extra == "snowflake"
+
+##Trilogy
+[![Website](https://img.shields.io/badge/INTRO-WEB-orange?)](https://trilogydata.dev/)
+[![Discord](https://img.shields.io/badge/DISCORD-CHAT-red?logo=discord)](https://discord.gg/Z4QSSuqGEd)
+
+pytrilogy is an experimental implementation of the Trilogy language, a higher-level SQL that replaces tables/joins with a lightweight semantic binding layer.
+
+Trilogy looks like SQL, but simpler. It's a modern SQL refresh targeted at SQL lovers who want reusability and simplicity with the power and iteratability of SQL. It compiles to SQL - making it easy to debug or integrate into existing workflows - and can be run against any supported SQL backend.  
+
+> [!TIP]
+> To get an overview of the language and run interactive examples, head to the [documentation](https://trilogydata.dev/).
+
+Installation: `pip install pytrilogy`
+
+`pytrilogy` can be run locally to parse and execute trilogy model [.preql] files using the `trilogy` CLI tool, or can be run in python by importing the `trilogy` package.
+
+You can read more about the project [here](https://trilogydata.dev/) and try out an interactive demo on the page an interactive demo [here](https://trilogydata.dev/demo). 
+
+Trilogy:
+```sql
+SELECT
+    name,
+    count(name) as name_count
+WHERE 
+    name='Elvis'
+ORDER BY
+    name_count desc
+LIMIT 10;
+```
+## Goals
+vs SQL, the goals are:
+
+Preserve:
+- Correctness
+- Accessibility
+
+Enhance:
+- Simplicity
+- Understandability
+- Refactoring/mantainability
+- Reusability
+
+Maintain:
+- Acceptable performance
+
+## Hello World
+
+Save the following code in a file named `hello.preql`
+
+```python
+key sentence_id int;
+property sentence_id.word_one string; # comments after a definition 
+property sentence_id.word_two string; # are syntactic sugar for adding
+property sentence_id.word_three string; # a description to it
+
+# comments in other places are just comments
+
+# define our datasources as queries in duckdb
+datasource word_one(
+    sentence: sentence_id,
+    word:word_one
+)
+grain(sentence_id)
+query '''
+select 1 as sentence, 'Hello' as word
+union all
+select 2, 'Bonjour'
+''';
+
+datasource word_two(
+    sentence: sentence_id,
+    word:word_two
+)
+grain(sentence_id)
+query '''
+select 1 as sentence, 'World' as word
+union all
+select 2 as sentence, 'World'
+''';
+
+datasource word_three(
+    sentence: sentence_id,
+    word:word_three
+)
+grain(sentence_id)
+query '''
+select 1 as sentence, '!' as word
+union all
+select 2 as sentence, '!'
+''';
+
+# an actual select statement
+# joins are automatically resolved between the 3 sources
+with sentences as
+select sentence_id, word_one || ' ' || word_two ||  word_three as text;
+
+SELECT
+    --sentences.sentence_id,
+    sentences.text
+WHERE 
+    sentences.sentence_id = 1
+;
+
+SELECT
+    --sentences.sentence_id,
+    sentences.text
+WHERE 
+    sentences.sentence_id = 2
+;
+# semicolon termination for all statements
+
+```
+
+Run the following from the directory the file is in.
+
+```bash
+trilogy run hello.trilogy duckdb
+```
+
+![UI Preview](./docs/hello_world.png)
+
+## Backends
+
+The current Trilogy implementation supports these backends:
+
+- Bigquery
+- SQL Server
+- DuckDB
+- Snowflake
+
+## Basic Example - Python
+
+Trilogy can be run directly in python.
+
+A bigquery example, similar to bigquery [the quickstart](https://cloud.google.com/bigquery/docs/quickstarts/query-public-dataset-console)
+
+```python
+
+
+from trilogy import Dialects, Environment
+
+environment = Environment()
+
+environment.parse('''
+
+key name string;
+key gender string;
+key state string;
+key year int;
+key yearly_name_count int; int;
+
+
+datasource usa_names(
+    name:name,
+    number:yearly_name_count,
+    year:year,
+    gender:gender,
+    state:state
+)
+address bigquery-public-data.usa_names.usa_1910_2013;
+
+'''
+)
+executor = Dialects.BIGQUERY.default_executor(environment=environment)
+
+results = executor.execute_text(
+'''SELECT
+    name,
+    sum(yearly_name_count) -> name_count 
+WHERE
+    name = 'Elvis'
+ORDER BY
+    name_count desc
+LIMIT 10;
+'''
+
+)
+# multiple queries can result from one text batch
+for row in results:
+    # get results for first query
+    answers = row.fetchall()
+    for x in answers:
+        print(x)
+```
+
+
+## Basic Example - CLI
+
+Trilogy can be run through a CLI tool, appropriately named 'trilogy'.
+
+After installing trilogy, you can run the trilogy CLI with two required positional arguments; the first the path to a file or a direct command,
+and second the dialect to run.
+
+`trilogy run <cmd or path to trilogy file> <dialect>`
+
+To pass arguments to a backend, append additional --<option> flags after specifying the dialect.
+
+Example:
+`trilogy run key in int; datasource test_source ( i:in) grain(in) address test; select in;" duckdb --path <path/to/duckdb>`
+
+### Bigquery Args
+N/A, only supports default auth. In python you can pass in a custom client.
+<TODO> support arbitrary cred paths. 
+
+### DuckDB Args
+- path <optional>
+
+### Postgres Args
+- host
+- port
+- username
+- password
+- database
+
+### Snowflake Args
+- account
+- username
+- password
+
+
+> [!TIP]
+> The CLI can also be used for formatting. PreQL has a default formatting style that should always be adhered to. `trilogy fmt <path to trilogy file>`
+
+
+## More Examples
+
+[Interactive demo](https://trilogydata.dev/demo). 
+
+Additional examples can be found in the [public model repository](https://github.com/trilogydata/trilogy-public-models).
+
+This is a good place to look for modeling examples.
+
+## Developing
+
+Clone repository and install requirements.txt and requirements-test.txt.
+
+## Contributing
+
+Please open an issue first to discuss what you would like to change, and then create a PR against that issue.
+
+## Similar in space
+
+"Better SQL" has been a popular space. We believe Trilogy takes a different approach then the following,
+but all are worth checking out. Please open PRs/comment for anything missed!
+
+
+- [malloy](https://github.com/malloydata/malloy)
+- [preql](https://github.com/erezsh/Preql)
+- [PREQL](https://github.com/PRQL/prql)

pytrilogy-0.0.1.102/README.md

@@ -0,0 +1,248 @@
+##Trilogy
+[![Website](https://img.shields.io/badge/INTRO-WEB-orange?)](https://trilogydata.dev/)
+[![Discord](https://img.shields.io/badge/DISCORD-CHAT-red?logo=discord)](https://discord.gg/Z4QSSuqGEd)
+
+pytrilogy is an experimental implementation of the Trilogy language, a higher-level SQL that replaces tables/joins with a lightweight semantic binding layer.
+
+Trilogy looks like SQL, but simpler. It's a modern SQL refresh targeted at SQL lovers who want reusability and simplicity with the power and iteratability of SQL. It compiles to SQL - making it easy to debug or integrate into existing workflows - and can be run against any supported SQL backend.  
+
+> [!TIP]
+> To get an overview of the language and run interactive examples, head to the [documentation](https://trilogydata.dev/).
+
+Installation: `pip install pytrilogy`
+
+`pytrilogy` can be run locally to parse and execute trilogy model [.preql] files using the `trilogy` CLI tool, or can be run in python by importing the `trilogy` package.
+
+You can read more about the project [here](https://trilogydata.dev/) and try out an interactive demo on the page an interactive demo [here](https://trilogydata.dev/demo). 
+
+Trilogy:
+```sql
+SELECT
+    name,
+    count(name) as name_count
+WHERE 
+    name='Elvis'
+ORDER BY
+    name_count desc
+LIMIT 10;
+```
+## Goals
+vs SQL, the goals are:
+
+Preserve:
+- Correctness
+- Accessibility
+
+Enhance:
+- Simplicity
+- Understandability
+- Refactoring/mantainability
+- Reusability
+
+Maintain:
+- Acceptable performance
+
+## Hello World
+
+Save the following code in a file named `hello.preql`
+
+```python
+key sentence_id int;
+property sentence_id.word_one string; # comments after a definition 
+property sentence_id.word_two string; # are syntactic sugar for adding
+property sentence_id.word_three string; # a description to it
+
+# comments in other places are just comments
+
+# define our datasources as queries in duckdb
+datasource word_one(
+    sentence: sentence_id,
+    word:word_one
+)
+grain(sentence_id)
+query '''
+select 1 as sentence, 'Hello' as word
+union all
+select 2, 'Bonjour'
+''';
+
+datasource word_two(
+    sentence: sentence_id,
+    word:word_two
+)
+grain(sentence_id)
+query '''
+select 1 as sentence, 'World' as word
+union all
+select 2 as sentence, 'World'
+''';
+
+datasource word_three(
+    sentence: sentence_id,
+    word:word_three
+)
+grain(sentence_id)
+query '''
+select 1 as sentence, '!' as word
+union all
+select 2 as sentence, '!'
+''';
+
+# an actual select statement
+# joins are automatically resolved between the 3 sources
+with sentences as
+select sentence_id, word_one || ' ' || word_two ||  word_three as text;
+
+SELECT
+    --sentences.sentence_id,
+    sentences.text
+WHERE 
+    sentences.sentence_id = 1
+;
+
+SELECT
+    --sentences.sentence_id,
+    sentences.text
+WHERE 
+    sentences.sentence_id = 2
+;
+# semicolon termination for all statements
+
+```
+
+Run the following from the directory the file is in.
+
+```bash
+trilogy run hello.trilogy duckdb
+```
+
+![UI Preview](./docs/hello_world.png)
+
+## Backends
+
+The current Trilogy implementation supports these backends:
+
+- Bigquery
+- SQL Server
+- DuckDB
+- Snowflake
+
+## Basic Example - Python
+
+Trilogy can be run directly in python.
+
+A bigquery example, similar to bigquery [the quickstart](https://cloud.google.com/bigquery/docs/quickstarts/query-public-dataset-console)
+
+```python
+
+
+from trilogy import Dialects, Environment
+
+environment = Environment()
+
+environment.parse('''
+
+key name string;
+key gender string;
+key state string;
+key year int;
+key yearly_name_count int; int;
+
+
+datasource usa_names(
+    name:name,
+    number:yearly_name_count,
+    year:year,
+    gender:gender,
+    state:state
+)
+address bigquery-public-data.usa_names.usa_1910_2013;
+
+'''
+)
+executor = Dialects.BIGQUERY.default_executor(environment=environment)
+
+results = executor.execute_text(
+'''SELECT
+    name,
+    sum(yearly_name_count) -> name_count 
+WHERE
+    name = 'Elvis'
+ORDER BY
+    name_count desc
+LIMIT 10;
+'''
+
+)
+# multiple queries can result from one text batch
+for row in results:
+    # get results for first query
+    answers = row.fetchall()
+    for x in answers:
+        print(x)
+```
+
+
+## Basic Example - CLI
+
+Trilogy can be run through a CLI tool, appropriately named 'trilogy'.
+
+After installing trilogy, you can run the trilogy CLI with two required positional arguments; the first the path to a file or a direct command,
+and second the dialect to run.
+
+`trilogy run <cmd or path to trilogy file> <dialect>`
+
+To pass arguments to a backend, append additional --<option> flags after specifying the dialect.
+
+Example:
+`trilogy run key in int; datasource test_source ( i:in) grain(in) address test; select in;" duckdb --path <path/to/duckdb>`
+
+### Bigquery Args
+N/A, only supports default auth. In python you can pass in a custom client.
+<TODO> support arbitrary cred paths. 
+
+### DuckDB Args
+- path <optional>
+
+### Postgres Args
+- host
+- port
+- username
+- password
+- database
+
+### Snowflake Args
+- account
+- username
+- password
+
+
+> [!TIP]
+> The CLI can also be used for formatting. PreQL has a default formatting style that should always be adhered to. `trilogy fmt <path to trilogy file>`
+
+
+## More Examples
+
+[Interactive demo](https://trilogydata.dev/demo). 
+
+Additional examples can be found in the [public model repository](https://github.com/trilogydata/trilogy-public-models).
+
+This is a good place to look for modeling examples.
+
+## Developing
+
+Clone repository and install requirements.txt and requirements-test.txt.
+
+## Contributing
+
+Please open an issue first to discuss what you would like to change, and then create a PR against that issue.
+
+## Similar in space
+
+"Better SQL" has been a popular space. We believe Trilogy takes a different approach then the following,
+but all are worth checking out. Please open PRs/comment for anything missed!
+
+
+- [malloy](https://github.com/malloydata/malloy)
+- [preql](https://github.com/erezsh/Preql)
+- [PREQL](https://github.com/PRQL/prql)

pytrilogy-0.0.1.102/pyproject.toml

@@ -0,0 +1,10 @@
+[tool.pytest.ini_options]
+markers = [
+    "adventureworks",
+    "adventureworks_execution",
+]
+log_cli_level="INFO"
+
+[tool.ruff]
+# Allow lines to be as long as 200 characters.
+line-length = 200