sqlframe 0.0.3__tar.gz → 1.0.0__tar.gz

{sqlframe-0.0.3 → sqlframe-1.0.0}/Makefile

@@ -8,10 +8,10 @@ slow-test:
 	pytest -n auto tests
 
 fast-test:
-	pytest -n auto tests/unit
+	pytest -n auto -m "fast"
 
 local-test:
-	pytest -n auto -m "local"
+	pytest -n auto -m "fast or local"
 
 bigquery-test:
 	pytest -n auto -m "bigquery"

{sqlframe-0.0.3 → sqlframe-1.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: sqlframe
-Version: 0.0.3
+Version: 1.0.0
 Summary: Taking the Spark out of PySpark by converting to SQL
 Home-page: https://github.com/eakmanrq/sqlframe
 Author: Ryan Eakman
@@ -30,8 +30,6 @@ License-File: LICENSE
   <img src="https://sqlframe.readthedocs.io/en/latest/docs/images/sqlframe_logo.png" alt="SQLFrame Logo" width="400"/>
 </div>
 
-![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)
-
 SQLFrame implements the PySpark DataFrame API in order to enable running transformation pipelines directly on database engines - no Spark clusters or dependencies required.
 
 SQLFrame currently supports the following engines (many more in development):

{sqlframe-0.0.3 → sqlframe-1.0.0}/README.md

@@ -2,8 +2,6 @@
   <img src="https://sqlframe.readthedocs.io/en/latest/docs/images/sqlframe_logo.png" alt="SQLFrame Logo" width="400"/>
 </div>
 
-![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)
-
 SQLFrame implements the PySpark DataFrame API in order to enable running transformation pipelines directly on database engines - no Spark clusters or dependencies required.
 
 SQLFrame currently supports the following engines (many more in development):

{sqlframe-0.0.3 → sqlframe-1.0.0}/blogs/sqlframe_universal_dataframe_api.md

@@ -9,7 +9,8 @@ SQL is the universal language that unites all data professionals, and it enables
 Despite its strengths, SQL often seems ill-suited for maintaining data pipelines.
 The language lacks support for abstracting common operations or unit testing specific segments of code, leading many to use Jinja as a makeshift solution. 
 Jinja SQL is to SQL what Pig Latin is to English - can be fun in small doses but impossible to understand at scale. 
-Moreover, SQL's repetitive nature, requiring columns to be repeated across operations, leads to fatigue and many data practitioners responding to the siren song of `SELECT *` and later found drowning in the sea of non-determinism.
+Furthermore, the repetitive nature of SQL, where columns must be specified repeatedly across operations, often leads to fatigue among data professionals. 
+This results in data professionals responding to the siren song of `SELECT *`, only to be later found drowning in the sea of non-determinism.
 
 This has put data professionals in a tough spot: Do you write your pipelines in SQL to favor accessibility or Python to favor maintainability? 
 Well, starting today, you no longer have to choose. 
@@ -25,7 +26,7 @@ You can finally have your cake and eat it too.
   <img src="../docs/images/sqlframe_logo.png" alt="SQLFrame Logo" width="800"/>
 </div>
 
-SQLFrame revolutionizes how data professionals interact with SQL and PySpark DataFrames. 
+[SQLFrame](https://github.com/eakmanrq/sqlframe) revolutionizes how data professionals interact with SQL and PySpark DataFrames. 
 Unlike traditional PySpark, SQLFrame converts DataFrame operations directly into SQL, enabling real-time SQL script generation during development. 
 Here's how it works:
 
@@ -133,7 +134,7 @@ Therefore not only does SQLFrame make your DataFrame pipeline more accessible, i
   <img src="images/you_get_pyspark_api.gif" alt="There is more" width="800"/>
 </div>
 
-SQLFrame currently supports BigQuery, DuckDB, and PostgreSQL, with Redshift, Snowflake, Spark, and Trino in development. 
-For those interested in experimenting with SQL generation for other engines, the "StandaloneSession" provides a flexible testing ground.
+SQLFrame currently supports [BigQuery](https://sqlframe.readthedocs.io/en/stable/bigquery/), [DuckDB](https://sqlframe.readthedocs.io/en/stable/duckdb/), and [Postgres](https://sqlframe.readthedocs.io/en/stable/postgres/), with Redshift, Snowflake, Spark, and Trino in development. 
+For those interested in experimenting with SQL generation for other engines, the [StandaloneSession](https://sqlframe.readthedocs.io/en/stable/standalone/) provides a flexible testing ground.
 
-Follow the simple setup guide to begin integrating SQLFrame into your projects today!
+Checkout the [README](https://github.com/eakmanrq/sqlframe) for more information on how to get started with SQLFrame!

sqlframe-1.0.0/pytest.ini

@@ -0,0 +1,7 @@
+[pytest]
+markers =
+    bigquery: test for BigQuery
+    duckdb: test for DuckDB
+    local: test that don't rely on external connections
+    postgres: test for Postgres
+addopts = -n 0 --dist=loadgroup

{sqlframe-0.0.3 → sqlframe-1.0.0}/setup.py

@@ -20,7 +20,7 @@ setup(
     python_requires=">=3.8",
     install_requires=[
         "prettytable<3.11.0",
-        "sqlglot>=23.14.0,<23.17",
+        "sqlglot>=23.14.0,<23.18",
     ],
     extras_require={
         "bigquery": [

{sqlframe-0.0.3 → sqlframe-1.0.0}/sqlframe/_version.py

@@ -12,5 +12,5 @@ __version__: str
 __version_tuple__: VERSION_TUPLE
 version_tuple: VERSION_TUPLE
 
-__version__ = version = '0.0.3'
-__version_tuple__ = version_tuple = (0, 0, 3)
+__version__ = version = '1.0.0'
+__version_tuple__ = version_tuple = (1, 0, 0)

{sqlframe-0.0.3 → sqlframe-1.0.0}/sqlframe.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: sqlframe
-Version: 0.0.3
+Version: 1.0.0
 Summary: Taking the Spark out of PySpark by converting to SQL
 Home-page: https://github.com/eakmanrq/sqlframe
 Author: Ryan Eakman
@@ -30,8 +30,6 @@ License-File: LICENSE
   <img src="https://sqlframe.readthedocs.io/en/latest/docs/images/sqlframe_logo.png" alt="SQLFrame Logo" width="400"/>
 </div>
 
-![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)
-
 SQLFrame implements the PySpark DataFrame API in order to enable running transformation pipelines directly on database engines - no Spark clusters or dependencies required.
 
 SQLFrame currently supports the following engines (many more in development):

{sqlframe-0.0.3 → sqlframe-1.0.0}/sqlframe.egg-info/requires.txt

@@ -1,5 +1,5 @@
 prettytable<3.11.0
-sqlglot<23.17,>=23.14.0
+sqlglot<23.18,>=23.14.0
 
 [bigquery]
 google-cloud-bigquery-storage<3,>=2

{sqlframe-0.0.3 → sqlframe-1.0.0}/tests/conftest.py

@@ -5,6 +5,12 @@ import time
 import pytest
 
 
+def pytest_collection_modifyitems(items, *args, **kwargs):
+    for item in items:
+        if not list(item.iter_markers()):
+            item.add_marker("fast")
+
+
 @pytest.fixture(scope="session", autouse=True)
 def set_tz():
     import os

{sqlframe-0.0.3 → sqlframe-1.0.0}/tests/integration/engines/bigquery/test_bigquery_session.py

@@ -17,4 +17,4 @@ def test_session_from_config():
     conn.cursor().execute("CREATE TABLE IF NOT EXISTS db1.test_table (cola INT, colb STRING)")
     session = BigQuerySession.builder.config("default_dataset", "sqlframe.db1").getOrCreate()
     columns = session.catalog.get_columns("test_table")
-    assert columns == {"cola": exp.DataType.build("BIGINT"), "colb": exp.DataType.build("TEXT")}
+    assert columns == {"`cola`": exp.DataType.build("BIGINT"), "`colb`": exp.DataType.build("TEXT")}

{sqlframe-0.0.3 → sqlframe-1.0.0}/tests/integration/engines/duck/test_duckdb_session.py

@@ -10,4 +10,4 @@ def test_session_from_config():
     conn.execute("CREATE TABLE test_table (cola INT, colb STRING)")
     session = DuckDBSession.builder.config("sqlframe.conn", conn).getOrCreate()
     columns = session.catalog.get_columns("test_table")
-    assert columns == {"cola": exp.DataType.build("INT"), "colb": exp.DataType.build("VARCHAR")}
+    assert columns == {'"cola"': exp.DataType.build("INT"), '"colb"': exp.DataType.build("VARCHAR")}

{sqlframe-0.0.3 → sqlframe-1.0.0}/tests/integration/engines/postgres/test_postgres_session.py

@@ -14,6 +14,6 @@ def test_session_from_config(function_scoped_postgres):
     ).getOrCreate()
     columns = session.catalog.get_columns("test_table")
     assert columns == {
-        "cola": exp.DataType.build("INT", dialect=session.output_dialect),
-        "colb": exp.DataType.build("STRING", dialect=session.output_dialect),
+        '"cola"': exp.DataType.build("INT", dialect=session.output_dialect),
+        '"colb"': exp.DataType.build("STRING", dialect=session.output_dialect),
     }

{sqlframe-0.0.3 → sqlframe-1.0.0}/tests/integration/engines/redshift/test_redshift_session.py

@@ -42,6 +42,6 @@ def test_session_from_config(cleanup_connector: RedshiftConnection):
     session = RedshiftSession.builder.config("sqlframe.conn", cleanup_connector).getOrCreate()
     columns = session.catalog.get_columns("dev.db1.test_table")
     assert columns == {
-        "cola": exp.DataType.build("INT", dialect=session.output_dialect),
-        "colb": exp.DataType.build("VARCHAR", dialect=session.output_dialect),
+        '"cola"': exp.DataType.build("INT", dialect=session.output_dialect),
+        '"colb"': exp.DataType.build("VARCHAR", dialect=session.output_dialect),
     }

{sqlframe-0.0.3 → sqlframe-1.0.0}/tests/integration/engines/test_engine_session.py

@@ -29,8 +29,15 @@ def test_session(cleanup_session: _BaseSession):
         cola_type = exp.DataType.build("DECIMAL", dialect=session.output_dialect)
     else:
         cola_type = exp.DataType.build("INT", dialect=session.output_dialect)
-    cola_name = '"COLA"' if session.output_dialect == "snowflake" else '"cola"'
-    colb_name = '"COLB"' if session.output_dialect == "snowflake" else '"colb"'
+    if session.output_dialect == "bigquery":
+        cola_name = "`cola`"
+        colb_name = "`colb`"
+    elif session.output_dialect == "snowflake":
+        cola_name = '"COLA"'
+        colb_name = '"COLB"'
+    else:
+        cola_name = '"cola"'
+        colb_name = '"colb"'
     assert columns == {
         cola_name: cola_type,
         colb_name: exp.DataType.build("VARCHAR", dialect=session.output_dialect)

sqlframe-0.0.3/pytest.ini

@@ -1,4 +0,0 @@
-[pytest]
-markers =
-    bigquery: test for BigQuery
-addopts = -n 0 --dist=loadgroup