tracesql

Name	tracesql JSON
Version	0.1.10 JSON
	download
home_page	None
Summary	None
upload_time	2024-12-12 16:16:51
maintainer	None
docs_url	None
author	None
requires_python	>=3.8
license	Apache License Version 2.0, January 2004 https://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "{}" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright {yyyy} {name of copyright owner} Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
keywords	tracesql sql lineage data lineage database snowflake bigquery
VCS
bugtrack_url
requirements	annotated-types pydantic pydantic-core typing-extensions
Travis-CI	No Travis.
coveralls test coverage	No coveralls.

            
## TOC

- [TraceSQL Python Package](#tracesql-python-package)
  - [Features](#features)
  - [Installation](#installation)
  - [Usage](#usage)
    - [Simple example](#simple-example)
  - [`analyze_lineage` method](#analyze_lineage-method)
    - [Parameters](#parameters)
    - [Response - `ApiResponse`](#response---apiresponse)
- [Data lineage](#data-lineage)
  - [Data lineage in SQL (technical view)](#data-lineage-in-sql-technical-view)
    - [Simple `SELECT`](#simple-select)
    - [Wildcard](#wildcard)
    - [Ambiguous Queries](#ambiguous-queries)



# TraceSQL Python Package

The `tracesql` Python is client for [TraceSQL](https://tracesql.com). It allows you to easily analyze SQL code for data lineage.


You can currently use this client and the API it wraps without any limitations or tokens. This might be changed in the future.


## Features

- Connects to TraceSQL API.
- Analyzes SQL code to generate data lineage.
- Outputs the lineage in JSON format.
- Generates an SVG image of the lineage.

## Installation

You can install the `tracesql` package via pip:

```bash
pip install tracesql
```

## Usage

### Simple example

```python
from tracesql import analyze_lineage

code = """
CREATE TABLE active_customers AS
SELECT customer_id, first_name || ' ' || last_name as fullname, email
FROM customers
WHERE status = 'active';
"""
response = analyze_lineage(code)

# Save the SVG image of the lineage
with open("image.svg", "w") as fw:
    fw.write(response.svg)

# Save the lineage data in JSON format
with open("lineage.json", "w") as fw:
    fw.write(response.lineage.model_dump_json(indent=2))

print("Lineage successfully saved in files.")
```

Here is output for this example:
![simple](examples/output/image.svg)


Optionally, you can provide DB model, which will help resolving ambiguous queries:
```
db_model = DbModel(
    tables=[
        DbModelTable(
            name="ACTIVE_CUSTOMERS",
            columns=["customer_id", "full_name", "email", "status"]
        ),
        DbModelTable(
            name="CUSTOMERS",
            columns=["customer_id", "full_name", "email", "status"]
        )
    ]
)
response = analyze_lineage(code, db_model=db_model)
```

When submitting database model, please ensure you use the correct case (upper/lower). The system is case-sensitive, and mismatches in casing (e.g., "Customers" vs "CUSTOMERS") may result in processing errors or unexpected behavior.

## `analyze_lineage` method

It provides the most basic interface for analyzing lineage. Check the underlaying code if you want to build something more capable.

### Parameters

- `query (str)`: The SQL query whose lineage you want to analyze.
- `db_model (Optional[DbModel])`: The database model containing the tables and columns used in the SQL query.

### Response - `ApiResponse`
- `svg`: A string representing the SVG image of the lineage.
- `lineage`: An object containing the lineage data in a pydantic class.


Each relation includes an attribute named `source_positions`, which provides detailed information about code, that is relevant for this relation:
```json
"source_positions": [
    {
        "start_idx": 109,
        "end_idx": 118
    }
    ...
]
```
The `start_idx` and `end_idx` represent character indices in the input SQL code. Together, they define a range that pinpoints the specific section of the code corresponding to the relation. These indices effectively serve as "pointers" to the relevant portion of the analyzed SQL query.


# Data lineage

Lineage traditionally refers to a person’s or group’s ancestry, tracing their origins and heritage through generations. It embodies the historical path that defines their roots and connections.

Similarly, data lineage traces the lifecycle of data, mapping its origins, transformations, and usage. It answers critical questions such as:

- Where did this data originate?
- How is this data used across systems or processes?
- What steps were involved in constructing this data?

More specific examples include:

- Can I safely delete this column?
- Are there scripts or processes that depend on this table?
- Who created or modified this data?

In a world where data is often more valuable than gold, it’s crucial to answer these questions quickly and accurately. This is why data lineage plays a vital role in effective data governance.

## Data lineage in SQL (technical view)

How is lineage created in SQL? It is as simple as creating a table:
```
CREATE TABLE NEW_TABLE
AS SELECT first_name, last_name from OLD_TABLE;
```
With this query, we have create lineage from `OLD_TABLE` to `NEW_TABLE`. On column level, this would look like this:
```
OLD_TABLE.first_name -> NEW_TABLE.first_name
OLD_TABLE.last_name -> NEW_TABLE.last_name
```

Lineage is created whenever data is moved or transformed. In SQL, this typically involves a `SELECT` statement to retrieve data before moving it, making `SELECT` the cornerstone of lineage analysis.

1. **Analyze `targets`** – Identify the destination of the `SELECT` statement, usually a single table.
2. **Analyze `sources`** – Identify the data sources, typically multiple tables referenced in the `FROM` clause.
3. **Connect `sources` and `targets`** – Establish relationships between sources and their corresponding targets.

### Simple `SELECT`

What happens when a `SELECT` statement has no explicit target?

```sql
SELECT name FROM accounts;
```

In most IDEs, this query simply displays the results. To model this behavior in lineage, we create an artificial target called `SELECT-RESULT`:

```
accounts.name -> SELECT-RESULT.name
```

This approach ensures the lineage remains consistent, even without a defined target.


### Wildcard

```sql
SELECT * FROM events;
```

This case is impossible to analyze without any extra info. We need to check the database model - view the columns of table `events`. You can either do this by providing the `CREATE TABLE` statement or you can provide the database model in JSON format directly to the API.


### Ambiguous Queries

Consider the following query:
```sql
SELECT price, name FROM products NATURAL JOIN suppliers;
```
Analyzing lineage in this case is challenging due to the absence of table aliases and fully qualified column names. Without these, it becomes unclear which table each column originates from.

While providing the database model to the lineage analyzer can help resolve this ambiguity, the best practice is to use explicit column references and table aliases to avoid confusion

```sql
SELECT p.price, s.name FROM products p
NATURAL JOIN suppliers s
```

This approach ensures clearer lineage analysis and reduces the risk of misinterpreting the data's origins.


            

Raw data

            {
    "_id": null,
    "home_page": null,
    "name": "tracesql",
    "maintainer": null,
    "docs_url": null,
    "requires_python": ">=3.8",
    "maintainer_email": null,
    "keywords": "tracesql, sql, lineage, data lineage, database, snowflake, bigquery",
    "author": null,
    "author_email": "Tomas Kukan <kukant96@gmail.com>",
    "download_url": "https://files.pythonhosted.org/packages/0d/33/e60761fb0fa4766e4ef3bec3363ef15eea79095f3b995da28c51c81f3dc7/tracesql-0.1.10.tar.gz",
    "platform": null,
    "description": "\n## TOC\n\n- [TraceSQL Python Package](#tracesql-python-package)\n  - [Features](#features)\n  - [Installation](#installation)\n  - [Usage](#usage)\n    - [Simple example](#simple-example)\n  - [`analyze_lineage` method](#analyze_lineage-method)\n    - [Parameters](#parameters)\n    - [Response - `ApiResponse`](#response---apiresponse)\n- [Data lineage](#data-lineage)\n  - [Data lineage in SQL (technical view)](#data-lineage-in-sql-technical-view)\n    - [Simple `SELECT`](#simple-select)\n    - [Wildcard](#wildcard)\n    - [Ambiguous Queries](#ambiguous-queries)\n\n\n\n# TraceSQL Python Package\n\nThe `tracesql` Python is client for [TraceSQL](https://tracesql.com). It allows you to easily analyze SQL code for data lineage.\n\n\nYou can currently use this client and the API it wraps without any limitations or tokens. This might be changed in the future.\n\n\n## Features\n\n- Connects to TraceSQL API.\n- Analyzes SQL code to generate data lineage.\n- Outputs the lineage in JSON format.\n- Generates an SVG image of the lineage.\n\n## Installation\n\nYou can install the `tracesql` package via pip:\n\n```bash\npip install tracesql\n```\n\n## Usage\n\n### Simple example\n\n```python\nfrom tracesql import analyze_lineage\n\ncode = \"\"\"\nCREATE TABLE active_customers AS\nSELECT customer_id, first_name || ' ' || last_name as fullname, email\nFROM customers\nWHERE status = 'active';\n\"\"\"\nresponse = analyze_lineage(code)\n\n# Save the SVG image of the lineage\nwith open(\"image.svg\", \"w\") as fw:\n    fw.write(response.svg)\n\n# Save the lineage data in JSON format\nwith open(\"lineage.json\", \"w\") as fw:\n    fw.write(response.lineage.model_dump_json(indent=2))\n\nprint(\"Lineage successfully saved in files.\")\n```\n\nHere is output for this example:\n![simple](examples/output/image.svg)\n\n\nOptionally, you can provide DB model, which will help resolving ambiguous queries:\n```\ndb_model = DbModel(\n    tables=[\n        DbModelTable(\n            name=\"ACTIVE_CUSTOMERS\",\n            columns=[\"customer_id\", \"full_name\", \"email\", \"status\"]\n        ),\n        DbModelTable(\n            name=\"CUSTOMERS\",\n            columns=[\"customer_id\", \"full_name\", \"email\", \"status\"]\n        )\n    ]\n)\nresponse = analyze_lineage(code, db_model=db_model)\n```\n\nWhen submitting database model, please ensure you use the correct case (upper/lower). The system is case-sensitive, and mismatches in casing (e.g., \"Customers\" vs \"CUSTOMERS\") may result in processing errors or unexpected behavior.\n\n## `analyze_lineage` method\n\nIt provides the most basic interface for analyzing lineage. Check the underlaying code if you want to build something more capable.\n\n### Parameters\n\n- `query (str)`: The SQL query whose lineage you want to analyze.\n- `db_model (Optional[DbModel])`: The database model containing the tables and columns used in the SQL query.\n\n### Response - `ApiResponse`\n- `svg`: A string representing the SVG image of the lineage.\n- `lineage`: An object containing the lineage data in a pydantic class.\n\n\nEach relation includes an attribute named `source_positions`, which provides detailed information about code, that is relevant for this relation:\n```json\n\"source_positions\": [\n    {\n        \"start_idx\": 109,\n        \"end_idx\": 118\n    }\n    ...\n]\n```\nThe `start_idx` and `end_idx` represent character indices in the input SQL code. Together, they define a range that pinpoints the specific section of the code corresponding to the relation. These indices effectively serve as \"pointers\" to the relevant portion of the analyzed SQL query.\n\n\n# Data lineage\n\nLineage traditionally refers to a person\u2019s or group\u2019s ancestry, tracing their origins and heritage through generations. It embodies the historical path that defines their roots and connections.\n\nSimilarly, data lineage traces the lifecycle of data, mapping its origins, transformations, and usage. It answers critical questions such as:\n\n- Where did this data originate?\n- How is this data used across systems or processes?\n- What steps were involved in constructing this data?\n\nMore specific examples include:\n\n- Can I safely delete this column?\n- Are there scripts or processes that depend on this table?\n- Who created or modified this data?\n\nIn a world where data is often more valuable than gold, it\u2019s crucial to answer these questions quickly and accurately. This is why data lineage plays a vital role in effective data governance.\n\n## Data lineage in SQL (technical view)\n\nHow is lineage created in SQL? It is as simple as creating a table:\n```\nCREATE TABLE NEW_TABLE\nAS SELECT first_name, last_name from OLD_TABLE;\n```\nWith this query, we have create lineage from `OLD_TABLE` to `NEW_TABLE`. On column level, this would look like this:\n```\nOLD_TABLE.first_name -> NEW_TABLE.first_name\nOLD_TABLE.last_name -> NEW_TABLE.last_name\n```\n\nLineage is created whenever data is moved or transformed. In SQL, this typically involves a `SELECT` statement to retrieve data before moving it, making `SELECT` the cornerstone of lineage analysis.\n\n1. **Analyze `targets`** \u2013 Identify the destination of the `SELECT` statement, usually a single table.\n2. **Analyze `sources`** \u2013 Identify the data sources, typically multiple tables referenced in the `FROM` clause.\n3. **Connect `sources` and `targets`** \u2013 Establish relationships between sources and their corresponding targets.\n\n### Simple `SELECT`\n\nWhat happens when a `SELECT` statement has no explicit target?\n\n```sql\nSELECT name FROM accounts;\n```\n\nIn most IDEs, this query simply displays the results. To model this behavior in lineage, we create an artificial target called `SELECT-RESULT`:\n\n```\naccounts.name -> SELECT-RESULT.name\n```\n\nThis approach ensures the lineage remains consistent, even without a defined target.\n\n\n### Wildcard\n\n```sql\nSELECT * FROM events;\n```\n\nThis case is impossible to analyze without any extra info. We need to check the database model - view the columns of table `events`. You can either do this by providing the `CREATE TABLE` statement or you can provide the database model in JSON format directly to the API.\n\n\n### Ambiguous Queries\n\nConsider the following query:\n```sql\nSELECT price, name FROM products NATURAL JOIN suppliers;\n```\nAnalyzing lineage in this case is challenging due to the absence of table aliases and fully qualified column names. Without these, it becomes unclear which table each column originates from.\n\nWhile providing the database model to the lineage analyzer can help resolve this ambiguity, the best practice is to use explicit column references and table aliases to avoid confusion\n\n```sql\nSELECT p.price, s.name FROM products p\nNATURAL JOIN suppliers s\n```\n\nThis approach ensures clearer lineage analysis and reduces the risk of misinterpreting the data's origins.\n\n",
    "bugtrack_url": null,
    "license": "Apache License Version 2.0, January 2004 https://www.apache.org/licenses/  TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION  1. Definitions.  \"License\" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.  \"Licensor\" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.  \"Legal Entity\" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, \"control\" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.  \"You\" (or \"Your\") shall mean an individual or Legal Entity exercising permissions granted by this License.  \"Source\" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.  \"Object\" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.  \"Work\" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).  \"Derivative Works\" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.  \"Contribution\" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, \"submitted\" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as \"Not a Contribution.\"  \"Contributor\" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.  2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.  3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.  4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:  (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and  (b) You must cause any modified files to carry prominent notices stating that You changed the files; and  (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and  (d) If the Work includes a \"NOTICE\" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.  You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.  5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.  6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.  7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.  8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.  9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.  END OF TERMS AND CONDITIONS  APPENDIX: How to apply the Apache License to your work.  To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets \"{}\" replaced with your own identifying information. (Don't include the brackets!)  The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same \"printed page\" as the copyright notice for easier identification within third-party archives.  Copyright {yyyy} {name of copyright owner}  Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at  https://www.apache.org/licenses/LICENSE-2.0  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ",
    "summary": null,
    "version": "0.1.10",
    "project_urls": {
        "Changelog": "https://github.com/tracesql/tracesql-py/blob/main/CHANGELOG.md",
        "Homepage": "https://tracesql.com",
        "Repository": "https://github.com/tracesql/tracesql-py"
    },
    "split_keywords": [
        "tracesql",
        " sql",
        " lineage",
        " data lineage",
        " database",
        " snowflake",
        " bigquery"
    ],
    "urls": [
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "b35283c01294c07a891b5a529f89ed6241748d8c2a4a47b8b49dc5f56c79d828",
                "md5": "36b5b5157880d0540ed0756851034815",
                "sha256": "4add6801ae254debc93491f6073fecf450304226198d19164938abe59d0be1ef"
            },
            "downloads": -1,
            "filename": "tracesql-0.1.10-py3-none-any.whl",
            "has_sig": false,
            "md5_digest": "36b5b5157880d0540ed0756851034815",
            "packagetype": "bdist_wheel",
            "python_version": "py3",
            "requires_python": ">=3.8",
            "size": 15776,
            "upload_time": "2024-12-12T16:16:48",
            "upload_time_iso_8601": "2024-12-12T16:16:48.526163Z",
            "url": "https://files.pythonhosted.org/packages/b3/52/83c01294c07a891b5a529f89ed6241748d8c2a4a47b8b49dc5f56c79d828/tracesql-0.1.10-py3-none-any.whl",
            "yanked": false,
            "yanked_reason": null
        },
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "0d33e60761fb0fa4766e4ef3bec3363ef15eea79095f3b995da28c51c81f3dc7",
                "md5": "7095ca6b98f297420ec95eb6d431797b",
                "sha256": "7dd7f83cbd9c4d95a934355a73f351d7a7e1264f11ec73432f7d827830bbcdc7"
            },
            "downloads": -1,
            "filename": "tracesql-0.1.10.tar.gz",
            "has_sig": false,
            "md5_digest": "7095ca6b98f297420ec95eb6d431797b",
            "packagetype": "sdist",
            "python_version": "source",
            "requires_python": ">=3.8",
            "size": 19895,
            "upload_time": "2024-12-12T16:16:51",
            "upload_time_iso_8601": "2024-12-12T16:16:51.014235Z",
            "url": "https://files.pythonhosted.org/packages/0d/33/e60761fb0fa4766e4ef3bec3363ef15eea79095f3b995da28c51c81f3dc7/tracesql-0.1.10.tar.gz",
            "yanked": false,
            "yanked_reason": null
        }
    ],
    "upload_time": "2024-12-12 16:16:51",
    "github": true,
    "gitlab": false,
    "bitbucket": false,
    "codeberg": false,
    "github_user": "tracesql",
    "github_project": "tracesql-py",
    "travis_ci": false,
    "coveralls": false,
    "github_actions": true,
    "requirements": [
        {
            "name": "annotated-types",
            "specs": [
                [
                    "==",
                    "0.7.0"
                ]
            ]
        },
        {
            "name": "pydantic",
            "specs": [
                [
                    "==",
                    "2.10.2"
                ]
            ]
        },
        {
            "name": "pydantic-core",
            "specs": [
                [
                    "==",
                    "2.27.1"
                ]
            ]
        },
        {
            "name": "typing-extensions",
            "specs": [
                [
                    "==",
                    "4.12.2"
                ]
            ]
        }
    ],
    "lcname": "tracesql"
}